Triple
T34637422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee and Virginia |
E889466
|
entity |
| Predicate | borderEstablishedDuring |
P14619
|
FINISHED |
| Object | 18th and 19th centuries |
—
|
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: 18th and 19th centuries | Statement: [Tennessee and Virginia, borderEstablishedDuring, 18th and 19th centuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderEstablishedDuring Context triple: [Tennessee and Virginia, borderEstablishedDuring, 18th and 19th centuries]
-
A.
borderEstablished
chosen
Indicates that a formal boundary between two geographic or political entities has been officially defined and put into effect.
-
B.
borderEstablishedAfter
Indicates that a border between entities was created or formally established after a specified time or event.
-
C.
borderOpening
Indicates that a border between two regions is being opened or made accessible for crossing or interaction.
-
D.
borderConfirmedBy
Indicates that the existence or delineation of a border is validated or officially recognized by a specified authority or source.
-
E.
borderPostIs
Indicates that one entity functions as a border post associated with or located at another entity.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff6c061c6c81909ff485e9cafc88a2 |
completed | May 9, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ff6aaf886c8190a3c87d089453f3de |
completed | May 9, 2026, 5:11 p.m. |
Created at: May 1, 2026, 2:04 a.m.