Triple
T9024726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2010 Canterbury earthquake |
E216016
|
entity |
| Predicate | utcDate |
P54655
|
FINISHED |
| Object | 2010-09-03 |
—
|
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: 2010-09-03 | Statement: [2010 Canterbury earthquake, utcDate, 2010-09-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: utcDate Context triple: [2010 Canterbury earthquake, utcDate, 2010-09-03]
-
A.
utcTime
chosen
Indicates that the associated time value is expressed in Coordinated Universal Time (UTC), independent of local time zones.
-
B.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
C.
relationToUTC
Indicates the temporal offset or correspondence between a given time value and Coordinated Universal Time (UTC).
-
D.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
E.
localTime
Indicates that a specific time value is expressed relative to a particular local time zone or locale, rather than in a universal or standardized time reference.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7b902c81909fcbdc433a1acf7a |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.