Triple
T23317354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Downeaster |
E590745
|
entity |
| Predicate | originalRouteEnd |
P51834
|
FINISHED |
| Object | Portland, Maine |
—
|
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: Portland, Maine | Statement: [Downeaster, originalRouteEnd, Portland, Maine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalRouteEnd Context triple: [Downeaster, originalRouteEnd, Portland, Maine]
-
A.
originalRoute
Indicates that one route is the initial or primary path from which another route is derived, modified, or compared.
-
B.
previousRoute
Indicates that one route directly precedes another in an ordered sequence of routes.
-
C.
formerRouteNumber
Indicates that an entity previously had a specific route number before being renumbered, discontinued, or otherwise changed.
-
D.
earlyRoute
Indicates that a route or path is taken or scheduled earlier than a standard, expected, or alternative route.
-
E.
endLocationOfJourney
chosen
Indicates the final destination or stopping point reached at the conclusion of a journey or trip.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197828c408190ae071624e40de4cc |
completed | April 29, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:06 p.m.