Triple
T26311139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockmetteller Todd |
E661823
|
entity |
| Predicate | isPressuredBy |
P51136
|
FINISHED |
| Object | Aunt Isabel Rockmetteller |
—
|
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: Aunt Isabel Rockmetteller | Statement: [Rockmetteller Todd, isPressuredBy, Aunt Isabel Rockmetteller]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPressuredBy Context triple: [Rockmetteller Todd, isPressuredBy, Aunt Isabel Rockmetteller]
-
A.
hasHumanPressure
Indicates that one entity exerts or experiences human-induced influence, stress, or impact in relation to another entity or environment.
-
B.
facedPressureFrom
chosen
Indicates that one entity experienced coercion, influence, or stress exerted by another entity to act or decide in a certain way.
-
C.
pressurized
Indicates that one entity exerts or maintains pressure on another, often creating a constrained or high-pressure condition.
-
D.
isPressingOf
Indicates that one entity is applying pressure or force onto another entity.
-
E.
pressurizedComparedTo
Indicates that one entity is under greater or lesser pressure relative to another entity.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60ee7e6348190951e6f9647f5555b |
completed | May 2, 2026, 2:49 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:22 p.m.