Triple
T14887082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaoyangmen station |
E359654
|
entity |
| Predicate | openingDateForLine |
P80363
|
FINISHED |
| Object | 1984 (Line 2) |
—
|
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: 1984 (Line 2) | Statement: [Chaoyangmen station, openingDateForLine, 1984 (Line 2)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingDateForLine Context triple: [Chaoyangmen station, openingDateForLine, 1984 (Line 2)]
-
A.
line2OpeningDate
chosen
Indicates the date on which the second line (e.g., a route, service, or facility line) was officially opened or began operation.
-
B.
openingDateToRapidTransit
Indicates the date on which a rapid transit service or connection was opened or became operational.
-
C.
openingDate_Line2
Indicates the secondary or alternative date on which something (such as a facility, service, or event) is opened or becomes operational.
-
D.
openingDateLine14
Indicates the date on which something (such as a service, facility, or record) is opened or begins operation, as specified in line 14 of a form or document.
-
E.
openingDateLine16
Indicates the date on which line 16 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded5f5b1c88190815f3585770cb135 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 2:07 a.m.