Triple
T36160396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W. O. Gant |
E1045858
|
entity |
| Predicate | residenceBasedOn |
P184967
|
FINISHED |
| Object | Asheville, North Carolina |
—
|
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: Asheville, North Carolina | Statement: [W. O. Gant, residenceBasedOn, Asheville, North Carolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residenceBasedOn Context triple: [W. O. Gant, residenceBasedOn, Asheville, North Carolina]
-
A.
residencyAt
Indicates that an entity lives or has an established residence at a particular location or address.
-
B.
hostResidenceOf
Indicates that a location serves as the primary place of residence for a specified person or group.
-
C.
inResidenceAt
Indicates that an entity lives or resides at a particular location or residence.
-
D.
hasResidenceOn
Indicates that one entity’s place of residence is located on or along another entity, such as a street, road, or other linear feature.
-
E.
hasResidenceIn
Indicates that an entity lives or maintains a primary dwelling in a specified location.
- F. None of above. chosen
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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b69a74a08190b31b1201278a2c57 |
completed | May 3, 2026, 8:56 p.m. |
Created at: May 3, 2026, 4:08 p.m.