Triple
T4573533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Cricket Council |
E123090
|
entity |
| Predicate | movedHeadquartersToDubai |
P57798
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [International Cricket Council, movedHeadquartersToDubai, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movedHeadquartersToDubai Context triple: [International Cricket Council, movedHeadquartersToDubai, 2005]
-
A.
movedHeadquartersFrom
Indicates that an entity relocated its main headquarters from one specified place to another.
-
B.
movedHeadquartersToMies
Indicates that an entity relocated its main headquarters to Mies.
-
C.
headquartersMovedOn
Indicates that the location of an entity’s headquarters changed on a specific date or point in time.
-
D.
establishesHeadquartersOf
Indicates that an entity selects and sets up the main administrative or operational center (headquarters) for another entity.
-
E.
temporaryHeadquartersLocation
Indicates the location where an entity is serving as a temporary headquarters for an organization or operation.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58c89a5c81909a78bf0ac64777ad |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5227063c8190973155a875b013a7 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56f6e75481909c487a94a2c2d0ba |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:10 p.m.