Triple
T8077562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shanghai Metro Line 1 |
E188529
|
entity |
| Predicate | northernExtensionOpeningDate |
P54234
|
FINISHED |
| Object | 1995-12-28 |
—
|
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: 1995-12-28 | Statement: [Shanghai Metro Line 1, northernExtensionOpeningDate, 1995-12-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: northernExtensionOpeningDate Context triple: [Shanghai Metro Line 1, northernExtensionOpeningDate, 1995-12-28]
-
A.
northLineExtensionOpeningDate
chosen
Indicates the date on which the extension of the North Line officially opened for service.
-
B.
expansionOpeningDate
Indicates the date on which an expansion of something (such as a facility, service, or project) was officially opened or became operational.
-
C.
northernBoundaryExtendedTo
Indicates that the northern boundary of one entity has been lengthened or expanded to reach or include another specified reference point or area.
-
D.
westEndOpeningDate
Indicates the calendar date on which a production or event first opened in London’s West End.
-
E.
officialOpeningDate
Indicates the calendar date on which something is formally inaugurated or officially opened for use or 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_69ca82b50c708190863f661d438e68df |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb40a184488190b19ef7066f0f5057 |
completed | March 31, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69cb049f1614819087360d1a4c6f0faa |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:28 p.m.