Triple
T10769748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 11 (Barcelona Metro) |
E254042
|
entity |
| Predicate | usesDriverlessOperation |
P3039
|
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 11 (Barcelona Metro), usesDriverlessOperation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDriverlessOperation Context triple: [Line 11 (Barcelona Metro), usesDriverlessOperation, true]
-
A.
isDriverless
chosen
Indicates that something operates or moves without a human driver controlling it.
-
B.
operatedWithout
Indicates that an action, process, or entity functioned or was carried out in the absence of a specified resource, condition, or participant.
-
C.
possibleDriver
Indicates that an entity is a candidate or potential driver of another entity, such as a possible cause, regulator, or influencing factor.
-
D.
isUncrewed
Indicates that an object, vehicle, or mission operates without any human crew physically on board.
-
E.
canBeUsedWithout
Indicates that one entity is capable of functioning or being utilized independently of another specified entity.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d732307fb88190ba1447f68523c58a |
completed | April 9, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69d6f311529c819080ca5493d55d6050 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.