Triple
T28134858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Hayes |
E714171
|
entity |
| Predicate | removesFromInfluence |
P165126
|
FINISHED |
| Object | Robert Kinsey |
—
|
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: Robert Kinsey | Statement: [Henry Hayes, removesFromInfluence, Robert Kinsey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removesFromInfluence Context triple: [Henry Hayes, removesFromInfluence, Robert Kinsey]
-
A.
removedFrom
Indicates that one entity has been taken away, extracted, or detached from another entity or context.
-
B.
removedFromCommandBy
Indicates that one entity was taken out of a position of command or authority by another entity.
-
C.
withdrewFrom
Indicates that one entity removed itself or its participation from another entity, context, or arrangement it was previously part of.
-
D.
removedAfter
Indicates that one entity is removed or deleted at a point in time that occurs after the removal or deletion of another entity.
-
E.
removedBefore
Indicates that one entity was removed or taken away earlier in time than another specified entity or event.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 27, 2026, 9:49 p.m.