Triple
T589764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Subway |
E17240
|
entity |
| Predicate | fullRevenueServiceStartDate |
P288
|
FINISHED |
| Object | 2023-01-07 |
—
|
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: 2023-01-07 | Statement: [Central Subway, fullRevenueServiceStartDate, 2023-01-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullRevenueServiceStartDate Context triple: [Central Subway, fullRevenueServiceStartDate, 2023-01-07]
-
A.
startDate
chosen
Indicates the point in time when an event, state, or relationship begins.
-
B.
coversPeriodStart
Indicates that the time span or coverage of one entity begins at, or includes, the specified starting point in time of another entity or period.
-
C.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
D.
inceptionDate
Indicates the date on which an entity, event, or relationship was first created, established, or began to exist.
-
E.
establishedAt
Indicates the specific time or date at which something (such as an organization, system, or entity) was founded or brought into existence.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bb775fc819085b968f8615dca59 |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cc13988190892ca10bd7ae9f09 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.