Triple
T33873453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leigh Anne Tuohy |
E868285
|
entity |
| Predicate | hasResidenceInPast |
P4907
|
FINISHED |
| Object | Tennessee |
E17093
|
NE 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: Tennessee | Statement: [Leigh Anne Tuohy, hasResidenceInPast, Tennessee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResidenceInPast Context triple: [Leigh Anne Tuohy, hasResidenceInPast, Tennessee]
-
A.
hasNearbyFormerResidenceOf
Indicates that one entity is located near a place that used to be the residence of another entity.
-
B.
hasResidenceIn
Indicates that an entity lives or maintains a primary dwelling in a specified location.
-
C.
hasSignificantResidence
Indicates that an entity maintains an important or primary place of residence at a specified location.
-
D.
hasResidency
Indicates that an entity holds an official, legally recognized residential status in a particular place or jurisdiction.
-
E.
formerResidenceOf
chosen
Indicates that a location was once the place where a person or entity lived or was based, but is no longer their current residence.
- F. None of above.
Provenance (4 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_69f34995029081909ede0f7df73d1a5e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36823252588190a54aeaa37e4d089a |
completed | June 20, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:47 a.m.