Triple
T34637430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee and Virginia |
E889466
|
entity |
| Predicate | shareCity |
P122449
|
FINISHED |
| Object | Bristol (divided between Tennessee and Virginia) |
—
|
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: Bristol (divided between Tennessee and Virginia) | Statement: [Tennessee and Virginia, shareCity, Bristol (divided between Tennessee and Virginia)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareCity Context triple: [Tennessee and Virginia, shareCity, Bristol (divided between Tennessee and Virginia)]
-
A.
city2
Indicates a relationship where one entity is identified as a city associated with, located in, or otherwise linked to another entity.
-
B.
cityOn
Indicates that a city is geographically located on a specified landform, area, or administrative region.
-
C.
otherCity
Indicates that one city is different from and not the same as another city.
-
D.
cityhoodBy
Indicates that an entity attained the status of a city through the action, decision, or authority of the referenced agent or process.
-
E.
cityIs
chosen
Indicates that one entity is a city associated with, or identified as, 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_6a0017dd31d08190aa5e9f72df83733a |
completed | May 10, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_6a0015a1deb88190b9cdaa60455b0a33 |
completed | May 10, 2026, 5:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.