Triple
T33380189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhenping Road |
E854750
|
entity |
| Predicate | line3ServiceStartDate |
P42368
|
FINISHED |
| Object | 2000-12-26 |
—
|
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-12-26 | Statement: [Zhenping Road, line3ServiceStartDate, 2000-12-26]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: line3ServiceStartDate Context triple: [Zhenping Road, line3ServiceStartDate, 2000-12-26]
-
A.
line3OpeningDate
chosen
Indicates the calendar date on which the third line (e.g., a route, service line, or similar system component) was officially opened or began operation.
-
B.
line13OpeningDate
Indicates the date on which line 13 was officially opened or began operation.
-
C.
lineSectionOpeningDate
Indicates the date on which a specific section of a line (e.g., a route, track, or corridor) was officially opened for use.
-
D.
line4OpeningDate
Indicates the date on which the fourth line (e.g., of a transit system or network) was officially opened or began operation.
-
E.
line2OpeningDate
Indicates the date on which the second line (e.g., a route, service, or facility line) was officially opened or began operation.
- 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_69f3496ca10c8190908640d18fa00832 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e00147d48190880fdcb31be37dcc |
completed | May 3, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69f6de0c821c8190ae3ebda9dfdd0064 |
completed | May 3, 2026, 5:33 a.m. |
Created at: May 1, 2026, 1:35 a.m.