Triple
T8462382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 1 (Shanghai Metro) |
E200073
|
entity |
| Predicate | isBusyLine |
P82777
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Line 1 (Shanghai Metro), isBusyLine, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBusyLine Context triple: [Line 1 (Shanghai Metro), isBusyLine, true]
-
A.
isOnLine
Indicates that one entity is located directly along, or in contact with, a specified line or linear path.
-
B.
hasLineUnderConstruction
Indicates that a line (such as a route, track, or service line) associated with an entity is currently in the process of being built, upgraded, or otherwise under construction.
-
C.
isShortLine
Indicates that a line is relatively short in length compared to a standard or other lines.
-
D.
isNextInLineTo
Indicates that one entity is immediately scheduled or positioned to receive something or assume a role after another entity.
-
E.
currentLineEstablished
Indicates that a particular line (such as a route, connection, or communication channel) has been successfully set up and is currently active.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4a251f08190840a7fc31ff528b5 |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:10 p.m.