Triple
T31630061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North East Line |
E807138
|
entity |
| Predicate | firstDriverlessHeavyMetro |
P155290
|
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: [North East Line, firstDriverlessHeavyMetro, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDriverlessHeavyMetro Context triple: [North East Line, firstDriverlessHeavyMetro, true]
-
A.
isDriverless
Indicates that something operates or moves without a human driver controlling it.
-
B.
isOnAutomatedMetroLine
chosen
Indicates that something (typically a metro station, segment, or service) belongs to or operates on a metro line that runs with automated (driverless or semi-driverless) train control.
-
C.
isFirstMetroLineInCity
Indicates that a metro line is the earliest or original metro line established in a given city.
-
D.
hasTramway
Indicates that a location or area is served by, contains, or is connected to a tramway system.
-
E.
rapidTransitSystem
Indicates a transportation relationship where people or goods are moved via a high-capacity, high-frequency public transit system designed for rapid travel over urban or regional routes.
- 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 10:44 p.m.