Triple
T5746159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee–North Carolina border |
E126736
|
entity |
| Predicate | historicallyDisputed |
P62867
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tennessee–North Carolina border, historicallyDisputed, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyDisputed Context triple: [Tennessee–North Carolina border, historicallyDisputed, yes]
-
A.
historicallyContestedBy
Indicates that two or more parties have disputed or challenged control, ownership, or interpretation of something over a period of history.
-
B.
historicallyContestedSince
Indicates that a subject has been the focus of dispute, disagreement, or contention starting from a specified point in time.
-
C.
associatedTerritoryDispute
chosen
Indicates that there is a territorial dispute or contested claim connected to the referenced entity or relationship.
-
D.
historicallyOpposedBy
Indicates that one entity has been the target of opposition, resistance, or antagonism from another entity over a historical period.
-
E.
disputed
Indicates that there is active disagreement or contestation over the validity, ownership, interpretation, or status of the relationship or claim between the entities.
- 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_69c0083179548190b384b0bf3c08ca4d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b52663c8190ab44258468d4296d |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021ca61688190875bd6107161c284 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:48 p.m.