Triple
T30638051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isabel Bradley |
E779897
|
entity |
| Predicate | exertsPsychologicalControlOver |
P93480
|
FINISHED |
| Object | Sophie MacDonald |
—
|
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: Sophie MacDonald | Statement: [Isabel Bradley, exertsPsychologicalControlOver, Sophie MacDonald]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exertsPsychologicalControlOver Context triple: [Isabel Bradley, exertsPsychologicalControlOver, Sophie MacDonald]
-
A.
exertsControlOver
Indicates that one entity has the power or authority to direct, influence, or determine the actions or decisions of another entity.
-
B.
emotionallyAbuses
chosen
Indicates that one entity subjects another to harmful, manipulative, or degrading emotional treatment.
-
C.
affectedControlOf
Indicates that one entity has influenced, altered, or impacted the degree of control another entity has over something.
-
D.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
-
E.
aimsToControl
Indicates an intention or effort by one entity to gain power over, direct, or regulate another entity or situation.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a52b3cc8190834c244c8012253d |
completed | May 2, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:29 p.m.