Triple
T33450974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caoyang Road |
E856638
|
entity |
| Predicate | line4ServiceStarted |
P41933
|
FINISHED |
| Object | 2005-12-31 |
—
|
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: 2005-12-31 | Statement: [Caoyang Road, line4ServiceStarted, 2005-12-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: line4ServiceStarted Context triple: [Caoyang Road, line4ServiceStarted, 2005-12-31]
-
A.
blueLineServiceBegan
Indicates that service on the Blue Line began operating at a specified time or event.
-
B.
line8Status
Indicates the status or condition associated with the eighth line in a sequence, record, or structured data set.
-
C.
line4OpeningDate
chosen
Indicates the date on which the fourth line (e.g., of a transit system or network) was officially opened or began operation.
-
D.
enteredServiceOnLine14
Indicates that an entity (such as a vehicle or piece of equipment) began operating in regular service on route or line 14.
-
E.
lineServed
Indicates that a particular transportation line (such as a bus, train, or metro line) provides service to or is operated at a given stop, station, or route segment.
- 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_69f3497281a08190b4705de0b5f26ba7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e4ab88b8819084f370c6640fe346 |
completed | May 3, 2026, 6:01 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:37 a.m.