Triple
T3726111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Railroad (of Massachusetts) |
E81752
|
entity |
| Predicate | routeDirectionFromBoston |
P14099
|
FINISHED |
| Object | north |
—
|
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: north | Statement: [Eastern Railroad (of Massachusetts), routeDirectionFromBoston, north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeDirectionFromBoston Context triple: [Eastern Railroad (of Massachusetts), routeDirectionFromBoston, north]
-
A.
directionFromBoston
chosen
Indicates the compass direction or bearing of one location as measured outward from Boston.
-
B.
distanceFromBoston
Indicates the spatial distance between a given entity’s location and the city of Boston.
-
C.
directionFromBristol
Indicates the cardinal or relative compass direction of one place or object as measured outward starting from Bristol.
-
D.
directionFromBelfast
Indicates the cardinal or relative compass direction of one place or object as measured outward from Belfast.
-
E.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcaf669d48190852aaeef70265404 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.