Triple
T31953028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston–Los Angeles |
E815831
|
entity |
| Predicate | easternAirportTerminus |
P99942
|
FINISHED |
| Object | Logan International Airport |
—
|
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: Logan International Airport | Statement: [Boston–Los Angeles, easternAirportTerminus, Logan International Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: easternAirportTerminus Context triple: [Boston–Los Angeles, easternAirportTerminus, Logan International Airport]
-
A.
easternTerminusLocatedOn
Indicates that the eastern endpoint of a route, line, or path is situated on or at a specified feature or location.
-
B.
westTerminalStation
Indicates that a station serves as the western terminal (end point) of a route, line, or service.
-
C.
easternTerminusTown
Indicates that a given town serves as the eastern endpoint or terminus of a route, line, or corridor.
-
D.
terminusAAirport
chosen
Indicates that an airport serves as the terminal (end) point for a specified air route or service.
-
E.
easternTerminusNearby
Indicates that the eastern endpoint of one entity is located close to the referenced entity.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2ac9bd481909a1e8adb4e294262 |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:08 a.m.