Triple
T19456289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bus 174 |
E486739
|
entity |
| Predicate | basedOnEventDate |
P830
|
FINISHED |
| Object | 2000-06-12 |
—
|
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: 2000-06-12 | Statement: [Bus 174, basedOnEventDate, 2000-06-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnEventDate Context triple: [Bus 174, basedOnEventDate, 2000-06-12]
-
A.
basedOnEvent
Indicates that something is derived from, influenced by, or determined in reference to a specific event.
-
B.
namedForEventDate
Indicates that something is named after or in reference to the date on which a particular event occurred.
-
C.
eventDateContext
Indicates the contextual role or significance that a specific date has within an event (e.g., whether it is the start, end, deadline, or another relevant temporal marker).
-
D.
basedOnEventsDescribedIn
Indicates that something is derived from, inspired by, or constructed using the events described in another source.
-
E.
dateOfRelatedEvent
chosen
Indicates that there is a specific date on which a related event associated with the subject occurs or occurred.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633c4088881908f23f25a82a513f6 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.