Triple
T31495664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xujiahui (Shanghai Metro) |
E803532
|
entity |
| Predicate | line1SectionOpened |
P172255
|
FINISHED |
| Object | 10 April 1993 |
—
|
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: 10 April 1993 | Statement: [Xujiahui (Shanghai Metro), line1SectionOpened, 10 April 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: line1SectionOpened Context triple: [Xujiahui (Shanghai Metro), line1SectionOpened, 10 April 1993]
-
A.
lineSectionOpenedWith
Indicates that a specific section of a line (such as a route, track, or service line) has been officially opened or put into operation by a particular action or event.
-
B.
line4SectionOpening
Indicates that a specific section of the fourth line is beginning or being opened.
-
C.
line1Section
Indicates that one entity is a specific section or segment of another entity referred to as "line1."
-
D.
line3OpeningSegment
Indicates that something is the initial or opening segment of a third line in a sequence or structure.
-
E.
lineBOpened
Indicates that a specific line B has been opened or activated, transitioning from a closed or inactive state.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a915ead881909463ae46419c343e |
completed | May 3, 2026, 1:47 a.m. |
Created at: April 30, 2026, 9:41 p.m.