Triple
T5494893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tournoi de France |
E144186
|
entity |
| Predicate | notableYearForHost |
P65058
|
FINISHED |
| Object | 1998 FIFA World Cup host year preparation |
—
|
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: 1998 FIFA World Cup host year preparation | Statement: [Tournoi de France, notableYearForHost, 1998 FIFA World Cup host year preparation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableYearForHost Context triple: [Tournoi de France, notableYearForHost, 1998 FIFA World Cup host year preparation]
-
A.
notableProductionHosted
Indicates that an entity has served as the host or venue for a notable production or show.
-
B.
notableDerbyHosted
Indicates that an entity has hosted a derby event considered notable or significant.
-
C.
notableDepictionYear
Indicates the year in which a notable or significant depiction of an entity occurred or was created.
-
D.
notableWorkYear
Indicates the year in which a notable work associated with an entity was created, released, or achieved prominence.
-
E.
coHostOf
Indicates a relationship where two or more entities jointly host the same event, program, or activity together.
- F. None of above. chosen
Provenance (4 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_69c008f5a2748190bce7a39aabf87a6d |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f08c2a4819093e772a1497c7ecc |
completed | March 22, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69c01b052f3c81909f71c6add0f35a6f |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f051e508190b3886d87b4afdd0b |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:31 p.m.