Triple
T29239396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eveanna Clutter |
E741276
|
entity |
| Predicate | residenceDuringNotableEvent |
P49534
|
FINISHED |
| Object | Kansas |
—
|
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: Kansas | Statement: [Eveanna Clutter, residenceDuringNotableEvent, Kansas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residenceDuringNotableEvent Context triple: [Eveanna Clutter, residenceDuringNotableEvent, Kansas]
-
A.
residenceDuringEvent
chosen
Indicates that an entity resides or is located at a particular place for the duration of a specified event.
-
B.
residenceDuringLife
Indicates that an entity lived or resided in a particular place during some period of its lifetime.
-
C.
hasFamousResidence
Indicates that an entity is associated with a residence that is widely recognized or notable.
-
D.
servedAsResidenceOf
Indicates that something functioned as the home or dwelling place of a particular person or group.
-
E.
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.
- 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_69f0911dd6fc819097d1abb287016489 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 12:30 p.m.