Triple
T27089341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Preston Burke |
E686117
|
entity |
| Predicate | hasResidenceInStory |
P98527
|
FINISHED |
| Object | Seattle |
—
|
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: Seattle | Statement: [Preston Burke, hasResidenceInStory, Seattle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResidenceInStory Context triple: [Preston Burke, hasResidenceInStory, Seattle]
-
A.
hasResidenceIn
Indicates that an entity lives or maintains a primary dwelling in a specified location.
-
B.
homeLocationInStory
chosen
Indicates the place that serves as a character’s primary home or base of residence within the context of the story.
-
C.
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.
-
D.
hasResidenceFeature
Indicates that a residence possesses or is characterized by a specific feature or attribute.
-
E.
stateOfFictionalResidence
Indicates the state or region in which a fictional character’s residence is located.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: April 27, 2026, 8:40 a.m.