Triple
T33163371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newport, Vermont |
E848808
|
entity |
| Predicate | hasBorderProximityInfluence |
P193557
|
FINISHED |
| Object | binational tourism |
—
|
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: binational tourism | Statement: [Newport, Vermont, hasBorderProximityInfluence, binational tourism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderProximityInfluence Context triple: [Newport, Vermont, hasBorderProximityInfluence, binational tourism]
-
A.
hasNearbyBoundary
Indicates that one entity’s boundary lies close to, but does not necessarily touch or coincide with, the boundary of another entity.
-
B.
hasBoundaryInfluenceFrom
Indicates that the boundary or limits of one entity are affected, shaped, or determined by another entity.
-
C.
nearStateBorderWith
Indicates that one entity is located close to the state border shared with another specified state or region.
-
D.
borderIsAffectedBy
Indicates that a border’s state, condition, or characteristics are influenced or changed by another factor or event.
-
E.
nearBorderDirection
Indicates that one entity is located close to a border or boundary in a specified directional orientation relative to that border.
- F. None of above. chosen
Provenance (4 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_69f3495be8808190bbf427733df08aad |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69fd49f612a4819096fe7d5a3bb439ba |
completed | May 8, 2026, 2:27 a.m. |
Created at: May 1, 2026, 1:28 a.m.