Triple
T18098882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newburyport station |
E433161
|
entity |
| Predicate | hasAdjacentBusConnections |
P15095
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Newburyport station, hasAdjacentBusConnections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentBusConnections Context triple: [Newburyport station, hasAdjacentBusConnections, yes]
-
A.
hasAdjacentBusStation
chosen
Indicates that one location has a bus station situated directly next to or very near it.
-
B.
hasPublicTransportConnection
Indicates that there is an available public transportation link or service connecting the related entities.
-
C.
hasFareGateConnectionTo
Indicates that there is a direct passage or connection between two areas that is controlled or mediated by fare gates.
-
D.
hasBusInterchange
Indicates that one transport-related entity includes, contains, or is associated with a bus interchange facility.
-
E.
hasPassengerRailConnection
Indicates that there exists a passenger rail service linking one location or transport node to another.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddb521448190b97d2b2aa7e4d7e6 |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:27 a.m.