Triple
T8726110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elias Conway |
E207134
|
entity |
| Predicate | officeAssumedByElection |
P6710
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Elias Conway, officeAssumedByElection, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeAssumedByElection Context triple: [Elias Conway, officeAssumedByElection, yes]
-
A.
officeAssumedByWinner
chosen
Indicates that a particular office or position is taken up or assumed by the winner of an election or contest.
-
B.
officeAssumedAfter
Indicates that one entity began holding an office or position after another entity had already assumed that same office.
-
C.
officeAssumedFrom
Indicates that one party has taken over or begun holding an office or position previously held by another party.
-
D.
officeAssumedByCurrentRepresentative
Indicates that the office in question is currently held by the representative who has assumed that position.
-
E.
appointedOrElected
Indicates that an entity attained a position, role, or office through either an appointment process or an electoral process.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d158b0481908249610458f97306 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.