Triple
T10559340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X Games |
E249172
|
entity |
| Predicate | featuresAthletesFrom |
P13494
|
FINISHED |
| Object | multiple countries |
—
|
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: multiple countries | Statement: [X Games, featuresAthletesFrom, multiple countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresAthletesFrom Context triple: [X Games, featuresAthletesFrom, multiple countries]
-
A.
athletesFrom
Indicates that one or more athletes originate from, represent, or are associated with a particular place or organization.
-
B.
featuresPlayer
Indicates that something includes or prominently presents a particular player as part of its content or composition.
-
C.
hasAthlete
Indicates a relationship where an entity (such as a team, organization, or event) includes or is associated with one or more athletes.
-
D.
featuresPlayersFrom
chosen
Indicates that something (such as a work, event, or production) includes or showcases players originating from a specified source, group, or location.
-
E.
formerAthlete
Indicates that a person previously had the role or status of an athlete but no longer does.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5271e65688190bcf7931373d87f94 |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:35 p.m.