Triple
T11539165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumas, Washington |
E273624
|
entity |
| Predicate | borderFacilityType |
P14206
|
FINISHED |
| Object | port of entry |
—
|
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: port of entry | Statement: [Sumas, Washington, borderFacilityType, port of entry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderFacilityType Context triple: [Sumas, Washington, borderFacilityType, port of entry]
-
A.
hasBorderFacilityType
chosen
Indicates that a border facility possesses or is classified by a specific type or category of border-related infrastructure or service.
-
B.
bordersFacility
Indicates that one facility or site lies directly adjacent to and shares a boundary with another facility.
-
C.
hasBorderControlFacility
Indicates that one location possesses an official facility responsible for managing and controlling border crossings to or from another location.
-
D.
crossBorderFacilityLocatedIn
Indicates that a cross-border facility is geographically situated within a specified territorial or administrative area.
-
E.
borderPostType
Indicates the specific kind or classification of a border post associated with a boundary or crossing point.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886deed5c81908e5c38156064f882 |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.