Triple
T29810183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houlton International Airport |
E756935
|
entity |
| Predicate | servesBorderTraffic |
P10963
|
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: [Houlton International Airport, servesBorderTraffic, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesBorderTraffic Context triple: [Houlton International Airport, servesBorderTraffic, yes]
-
A.
hasBorderTrafficControl
Indicates that there is an official system or mechanism in place to monitor, regulate, or manage the movement of people or goods across a border.
-
B.
hasBorderCrossingFunction
chosen
Indicates that an entity serves as a location or facility where people, goods, or vehicles can legally cross a border between jurisdictions.
-
C.
borderTerminus
Indicates the endpoint location where a border between two areas or entities begins or ends.
-
D.
handlesInternationalTrafficAt
Indicates that an entity manages or processes international traffic at a specified location or facility.
-
E.
borderStation
Indicates a facility or checkpoint located at or near a border where cross-boundary movement, control, or processing of people or goods occurs.
- 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: April 29, 2026, 5:23 p.m.