Triple
T37501842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canada–United States border crossings |
E931983
|
entity |
| Predicate | includeMode |
P171380
|
FINISHED |
| Object | land crossings |
—
|
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: land crossings | Statement: [Canada–United States border crossings, includeMode, land crossings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeMode Context triple: [Canada–United States border crossings, includeMode, land crossings]
-
A.
mayIncludeMode
Indicates that one entity is allowed to contain or support a particular mode as one of its possible configurations or options.
-
B.
includesSee
Indicates that one entity’s scope, content, or experience contains or encompasses the act of seeing or visual perception involving another entity.
-
C.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
D.
includedByDefaultIn
Indicates that one entity is automatically present or enabled within another entity or context without requiring explicit selection or configuration.
-
E.
includesModality
chosen
Indicates that one element incorporates or specifies a particular modality (such as mode, manner, or form) in relation to another.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.