Triple
T2526960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maple Leaf |
E56056
|
entity |
| Predicate | borderControlLocation |
P14205
|
FINISHED |
| Object | onboard at the border |
—
|
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: onboard at the border | Statement: [Maple Leaf, borderControlLocation, onboard at the border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderControlLocation Context triple: [Maple Leaf, borderControlLocation, onboard at the border]
-
A.
borderControlSide
Indicates that one entity is positioned on or associated with a particular side or segment of a border control area or checkpoint.
-
B.
borderControls
Indicates that one entity enforces or administers border control measures over another entity or at a specific boundary.
-
C.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
D.
crossBorderFacilityLocatedIn
chosen
Indicates that a cross-border facility is geographically situated within a specified territorial or administrative area.
-
E.
hasBorderControlStatus
Indicates the type or condition of border control that applies to a given entity or location.
- 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_69ab4a48e4f081908f1218d244608659 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd255f0d081908d20cfb812c4bfc1 |
completed | March 7, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69abd0c2e34c8190a914d5c2afba147c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.