Triple
T891221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chair M |
E19241
|
entity |
| Predicate | successorRelation |
P78
|
FINISHED |
| Object | new member elected when the seat becomes vacant |
—
|
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: new member elected when the seat becomes vacant | Statement: [Chair M, successorRelation, new member elected when the seat becomes vacant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorRelation Context triple: [Chair M, successorRelation, new member elected when the seat becomes vacant]
-
A.
successorOperator
Indicates that one operator directly follows another in a defined sequence or ordering.
-
B.
successor
chosen
Indicates that one entity directly follows another in an ordered sequence or position.
-
C.
successorLine
Indicates that one line directly follows another in a sequence or ordered arrangement.
-
D.
eventualSuccessor
Indicates that one entity will become the successor of another at some later point in time, rather than immediately.
-
E.
successorFunction
Indicates the relationship where one entity is defined as the immediate next or following element in a sequence or ordered set relative to another.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad019e448190ab991e85dc6d7708 |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa9372e88190b5a9db4afdc045c6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.