Triple
T662917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aunt Polly |
E11795
|
entity |
| Predicate | settingOfResidence |
P75
|
FINISHED |
| Object | Mississippi River town |
—
|
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: Mississippi River town | Statement: [Aunt Polly, settingOfResidence, Mississippi River town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfResidence Context triple: [Aunt Polly, settingOfResidence, Mississippi River town]
-
A.
residencyPattern
Indicates the typical way an entity resides or occupies a place over time, such as its usual location, duration, or frequency of stay.
-
B.
residence
chosen
Indicates that one entity lives at, is based in, or habitually occupies the location represented by the other entity.
-
C.
formerResidenceOf
Indicates that a location was once the place where a person or entity lived or was based, but is no longer their current residence.
-
D.
residenceCountry
Indicates the country in which an entity lives or has their primary place of residence.
-
E.
residenceType
Indicates the kind or category of dwelling or living arrangement associated with an 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49fd081e8819097f289961f5eff29 |
completed | March 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69a49d153a948190b3ccdc331ed33617 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.