Triple
T9667407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U-17 |
E233739
|
entity |
| Predicate | typicalCompetitionFrequency |
P30335
|
FINISHED |
| Object | annual or biennial tournaments |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: annual or biennial tournaments | Statement: [U-17, typicalCompetitionFrequency, annual or biennial tournaments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCompetitionFrequency Context triple: [U-17, typicalCompetitionFrequency, annual or biennial tournaments]
-
A.
levelOfCompetition
Indicates the intensity or degree of competitive pressure present in a given context or interaction.
-
B.
gamesFrequency
chosen
Indicates how often the related entities engage in playing games together or participate in game-related activities.
-
C.
typicalCompetitionArea
Indicates the usual or standard geographic or contextual area in which a competition or competitive activity typically takes place.
-
D.
typeOfCompetition
Indicates the specific kind or category of competition in which an entity participates or is involved.
-
E.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c3c06e4819080c1b8e66faa482f |
completed | April 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.