Triple
T8601305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 8 (Shanghai Metro) |
E203680
|
entity |
| Predicate | hasSectionOpening |
P83802
|
FINISHED |
| Object | 2007-12-29 |
—
|
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: 2007-12-29 | Statement: [Line 8 (Shanghai Metro), hasSectionOpening, 2007-12-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSectionOpening Context triple: [Line 8 (Shanghai Metro), hasSectionOpening, 2007-12-29]
-
A.
isOpeningSectionOf
Indicates that one content segment functions as the initial or introductory section of another, larger work or structure.
-
B.
hasSectionOn
Indicates that one entity (typically a document or resource) contains a dedicated section or part that specifically addresses or discusses another entity or topic.
-
C.
hasSectionIn
Indicates that one entity contains or includes another entity as a section or subdivision within it.
-
D.
hasSect
Indicates that an entity includes, contains, or is associated with a particular sect or subgroup within a larger religious, ideological, or organizational context.
-
E.
hasOpeningBridgeSection
Indicates that one entity (typically a musical work or section) contains an initial bridge section at its opening.
- 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46d8ff408190acc7cd8dc99b2689 |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:24 p.m.