Triple
T34432456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L3 (Barcelona Metro) |
E883863
|
entity |
| Predicate | openedAsMetro |
P28350
|
FINISHED |
| Object | 1924 |
—
|
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: 1924 | Statement: [L3 (Barcelona Metro), openedAsMetro, 1924]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsMetro Context triple: [L3 (Barcelona Metro), openedAsMetro, 1924]
-
A.
openedAsMetroExtension
Indicates that a transportation line, station, or segment was inaugurated specifically as part of an extension to an existing metro system.
-
B.
openedAsMetraService
Indicates that a transportation facility or line began operating specifically as part of the Metra commuter rail service.
-
C.
openedAsMetroNorthService
Indicates that a transportation facility or line began operation specifically as part of the Metro-North Railroad service.
-
D.
openedAsMBTAService
Indicates that a transit facility or line began operation specifically as part of the MBTA (Massachusetts Bay Transportation Authority) service.
-
E.
openedAsSubway
chosen
Indicates that a transportation facility or line originally began operation specifically as a subway service.
- 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: May 1, 2026, 2 a.m.