Triple
T8859344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 5 (Shanghai Metro) |
E210845
|
entity |
| Predicate | openingStage |
P85027
|
FINISHED |
| Object | Xinzhuang–Jinping Road section opened 2003 |
—
|
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: Xinzhuang–Jinping Road section opened 2003 | Statement: [Line 5 (Shanghai Metro), openingStage, Xinzhuang–Jinping Road section opened 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingStage Context triple: [Line 5 (Shanghai Metro), openingStage, Xinzhuang–Jinping Road section opened 2003]
-
A.
openingTo
Indicates that one entity serves as an entrance, access point, or passage leading into or toward another entity.
-
B.
openingPerformance
Indicates the performance or event that serves as the first or inaugural showing in a series, season, or run.
-
C.
openingSituation
Indicates the initial state, context, or set of conditions that exist at the beginning of an event, interaction, or narrative.
-
D.
openingBegan
Indicates that the process of opening something has started.
-
E.
openingWorkOf
Indicates that one work serves as the first or introductory piece in relation to another work, such as the opening item in a sequence or collection.
- F. None of above. chosen
Provenance (4 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_69ca838bbddc8190ab546d737e5d350f |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60e536648190ba8da1375478c24f |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cffe8ec819084c12770fe0578f2 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:50 p.m.