Triple
T5603677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Africa vs Mexico 2010 FIFA World Cup opening match |
E147180
|
entity |
| Predicate | kickoffTimeUTC |
P54655
|
FINISHED |
| Object | 14:00 |
—
|
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: 14:00 | Statement: [South Africa vs Mexico 2010 FIFA World Cup opening match, kickoffTimeUTC, 14:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kickoffTimeUTC Context triple: [South Africa vs Mexico 2010 FIFA World Cup opening match, kickoffTimeUTC, 14:00]
-
A.
typicalKickoffTimeEastern
Indicates the usual starting time of an event, expressed in the Eastern Time zone.
-
B.
impactTimeEasternDaylightTime
Indicates the specific time at which an impact occurs, expressed in Eastern Daylight Time.
-
C.
isNinetyMinutesAheadOf
Indicates that one entity occurs or is positioned exactly ninety minutes later in time than another entity.
-
D.
utcTime
chosen
Indicates that the associated time value is expressed in Coordinated Universal Time (UTC), independent of local time zones.
-
E.
minuteOfOpeningGoal
Indicates the specific minute in a match when the first (opening) goal is scored.
- 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020dce10c8190bf456602eec211d4 |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1890ec8190b9e6fa488792e4d4 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.