Triple
T9285610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earthquake Game |
E223387
|
entity |
| Predicate | scheduledStartTime |
P12530
|
FINISHED |
| Object | 1989-10-17T17:35:00-07: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: 1989-10-17T17:35:00-07:00 | Statement: [Earthquake Game, scheduledStartTime, 1989-10-17T17:35:00-07:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scheduledStartTime Context triple: [Earthquake Game, scheduledStartTime, 1989-10-17T17:35:00-07:00]
-
A.
scheduledDuring
Indicates that one event or activity is planned to occur within the time interval defined by another event or period.
-
B.
scheduledAs
Indicates that one entity is assigned or arranged to occur or function in the role, time, or capacity specified by another entity within a schedule.
-
C.
startsAt
chosen
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
D.
requiresStartTime
Indicates that an entity cannot be valid, initiated, or executed unless a specific start time has been provided or is in effect.
-
E.
estimatedStartDate
Indicates the date on which something is expected or planned to begin, based on current information or projections.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd081fe8cc8190b6c1b481c7129689 |
completed | April 1, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:35 p.m.