Triple
T596414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RALE |
E17392
|
entity |
| Predicate | roleOnLine |
P15096
|
FINISHED |
| Object | northern terminus of the MBTA Red Line |
—
|
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: northern terminus of the MBTA Red Line | Statement: [RALE, roleOnLine, northern terminus of the MBTA Red Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOnLine Context triple: [RALE, roleOnLine, northern terminus of the MBTA Red Line]
-
A.
roleAtMidway
Indicates that an entity holds or held a specific role, position, or function at the midpoint or intermediate stage of a process, event, or time period.
-
B.
isOnLine
chosen
Indicates that one entity is located directly along, or in contact with, a specified line or linear path.
-
C.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
D.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
E.
role
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bd3e5e08190be95cb2009aad42d |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cfb52c81908d816a4c5579c321 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.