Triple
T18805578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mia Warren |
E459864
|
entity |
| Predicate | upends |
P133080
|
FINISHED |
| Object | lives of Shaker Heights residents |
—
|
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: lives of Shaker Heights residents | Statement: [Mia Warren, upends, lives of Shaker Heights residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upends Context triple: [Mia Warren, upends, lives of Shaker Heights residents]
-
A.
upset
Indicates that one entity causes another to feel distressed, unhappy, or emotionally disturbed.
-
B.
underpins
Indicates that one entity serves as the fundamental basis, support, or justification for another.
-
C.
under
Indicates that one entity is positioned below or beneath another entity, often implying vertical alignment or coverage.
-
D.
endsUp
Indicates that one entity ultimately arrives at, becomes, or results in another state, condition, or location after some process or sequence of events.
-
E.
over
Indicates that one entity is positioned higher than and extending across or above another entity, often covering or spanning it.
- F. None of above. chosen
Provenance (4 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a3d6d5e081909d8285e52cb753ba |
completed | April 20, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:53 a.m.