Triple
T968459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RideKC Streetcar |
E20890
|
entity |
| Predicate | startOfRevenueService |
P3267
|
FINISHED |
| Object | 2016-05-06 |
—
|
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: 2016-05-06 | Statement: [RideKC Streetcar, startOfRevenueService, 2016-05-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfRevenueService Context triple: [RideKC Streetcar, startOfRevenueService, 2016-05-06]
-
A.
operationStart
chosen
Indicates the point in time or event at which a specific operation or process begins.
-
B.
startProperty
Indicates that one entity marks the beginning or initial value/state of a property associated with another entity.
-
C.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
D.
starterType
Indicates the classification or category of a starter (e.g., initial component, opening item, or first phase) associated with an entity or process.
-
E.
startTimeAsRepresentative
Indicates the time at which an entity begins serving or acting in a representative capacity.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b4481f508190adcf0a965a23862c |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a579888190afb489ac9fe8391c |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.