Triple
T32547736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rebibbia–Laurentina branch of Line B |
E831889
|
entity |
| Predicate | connectsWithOtherLineAt |
P35426
|
FINISHED |
| Object | Termini station |
—
|
NE NERFINISHED |
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: Termini station | Statement: [Rebibbia–Laurentina branch of Line B, connectsWithOtherLineAt, Termini station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsWithOtherLineAt Context triple: [Rebibbia–Laurentina branch of Line B, connectsWithOtherLineAt, Termini station]
-
A.
connectedLine
Indicates that two entities are joined by a continuous line or linear connection.
-
B.
connectionLine
Indicates a direct link or path that connects two entities within a system or structure.
-
C.
connectedByStraitTo
Indicates that one entity is geographically linked to another by a narrow body of water known as a strait.
-
D.
associatedLine
Indicates that one entity is linked or connected to a particular line (such as a line item, line of text, or line in a structure) with which it is contextually or functionally related.
-
E.
connectsToMainLineAt
chosen
Indicates that one entity is linked or joined to a primary or central line at a specific point.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
Created at: May 1, 2026, 1:02 a.m.