Triple
T13538345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World11 |
E323317
|
entity |
| Predicate | timeAssociatedWith |
P11533
|
FINISHED |
| Object | date of annual World XI reveal |
—
|
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: date of annual World XI reveal | Statement: [World11, timeAssociatedWith, date of annual World XI reveal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeAssociatedWith Context triple: [World11, timeAssociatedWith, date of annual World XI reveal]
-
A.
associatedWithTime
chosen
Indicates a relationship where something is linked or connected to a specific point or period in time.
-
B.
timeCorrelation
Indicates that two events or states are related in time such that changes or occurrences in one are systematically associated with changes or occurrences in the other.
-
C.
timeRecorded
Indicates that a specific point or period in time has been captured and stored as associated with an event, action, or state.
-
D.
time
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
-
E.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafd7ad9481908fe1d7ffcf8fab71 |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:45 p.m.