Triple
T37913910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vermont state boundary system |
E945758
|
entity |
| Predicate | hasHistoricalDisputeWith |
P3572
|
FINISHED |
| Object | State of New York |
—
|
NE NERFINISHED |
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: State of New York | Statement: [Vermont state boundary system, hasHistoricalDisputeWith, State of New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalDisputeWith Context triple: [Vermont state boundary system, hasHistoricalDisputeWith, State of New York]
-
A.
hasDisputeHistory
chosen
Indicates that there has been at least one prior dispute or conflict involving the related entities.
-
B.
hasDisputeWith
Indicates that there is a conflict, disagreement, or contested issue between two entities.
-
C.
hasDisputedStatusWith
Indicates that there is a contested or unresolved status, claim, or standing between the related entities.
-
D.
hasDisputedStatus
Indicates that the status or classification of something is contested, uncertain, or not universally agreed upon.
-
E.
hasDisputeRegime
Indicates that there exists a specific dispute-handling framework, system, or set of rules governing how disputes related to the subject are managed or resolved.
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffab5adf2c819084700c5ea34615bf |
completed | May 9, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69ffaabffa208190b5214ca17cc8a5ea |
completed | May 9, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:20 p.m.