Triple
T31814978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joy "Ma" Newsome |
E812108
|
entity |
| Predicate | residesInAfterEscape |
P59130
|
FINISHED |
| Object | her parents' house |
—
|
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: her parents' house | Statement: [Joy "Ma" Newsome, residesInAfterEscape, her parents' house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residesInAfterEscape Context triple: [Joy "Ma" Newsome, residesInAfterEscape, her parents' house]
-
A.
afterEscape
chosen
Indicates that one event, state, or action occurs subsequent to or as a consequence of an escape.
-
B.
residenceAfterDefection
Indicates that an entity’s place of residence is located in or associated with another entity after the entity has defected from a previous affiliation or location.
-
C.
residenceAfterRelease
Indicates the place where an individual lives or is located following their release from a prior confinement, custody, or institutional stay.
-
D.
residenceAfterRescue
Indicates that an entity’s place of residence after being rescued is the specified location.
-
E.
statementAfterEscape
Indicates that a statement or declaration occurs after an escape event or successful act of escaping.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 30, 2026, 11:44 p.m.