Triple
T11744560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee and Arkansas |
E279243
|
entity |
| Predicate | shareInterstateBoundaryEstablished |
P47901
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Tennessee and Arkansas, shareInterstateBoundaryEstablished, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareInterstateBoundaryEstablished Context triple: [Tennessee and Arkansas, shareInterstateBoundaryEstablished, 19th century]
-
A.
hasInterstate
Indicates that there exists an interstate connection or highway link between the related entities.
-
B.
fareBoundaryBetween
Indicates that there is a dividing line or zone where one fare region, zone, or pricing scheme ends and another begins.
-
C.
nearInternationalBoundary
Indicates that one entity is located close to an international boundary separating two or more countries.
-
D.
provinceBordering
Indicates that two provinces share a common boundary or border with each other.
-
E.
isPoliticalBoundary
chosen
Indicates that one entity serves as a dividing line or border that separates distinct political or administrative jurisdictions.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4f2a38c8190a682d8dae1ab9415 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.