Triple
T1195092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CONCACAF U-17 Championship |
E25649
|
entity |
| Predicate | playerCategory |
P6384
|
FINISHED |
| Object | male youth players |
—
|
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: male youth players | Statement: [CONCACAF U-17 Championship, playerCategory, male youth players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerCategory Context triple: [CONCACAF U-17 Championship, playerCategory, male youth players]
-
A.
participantType
chosen
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
B.
raceCategory
Indicates the classification of an entity into a specific race or racial group within a defined categorization system.
-
C.
memberCategory
Indicates that an entity belongs to or is classified under a specific category or group.
-
D.
registrationCategory
Indicates the classification or type under which an entity is formally registered within a system or registry.
-
E.
uniformCategory
Indicates that two or more entities share the same classification or type within a defined category system.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd78f61c8190bdba2255d35a8fe4 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5d40a08190b7682d8ef8075421 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.