Triple
T25211259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose Cumberbatch |
E631691
|
entity |
| Predicate | livesInFormerResidenceOfCharacter |
P18745
|
FINISHED |
| Object | Archie Bunker |
—
|
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: Archie Bunker | Statement: [Rose Cumberbatch, livesInFormerResidenceOfCharacter, Archie Bunker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livesInFormerResidenceOfCharacter Context triple: [Rose Cumberbatch, livesInFormerResidenceOfCharacter, Archie Bunker]
-
A.
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.
-
B.
laterLivedIn
chosen
Indicates that one entity resided in a particular place during a later period of its life, after an earlier residence elsewhere.
-
C.
hasNearbyFormerResidenceOf
Indicates that one entity is located near a place that used to be the residence of another entity.
-
D.
inResidenceAt
Indicates that an entity lives or resides at a particular location or residence.
-
E.
usedAtResidence
Indicates that an object, resource, or service is utilized within or for the purposes of a particular 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47b8918fc819080825ed92fb3a1a7 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 12:58 p.m.