Triple
T597227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junior Warden |
E11412
|
entity |
| Predicate | electedOrAppointed |
P11399
|
FINISHED |
| Object | elected in many jurisdictions |
—
|
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: elected in many jurisdictions | Statement: [Junior Warden, electedOrAppointed, elected in many jurisdictions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electedOrAppointed Context triple: [Junior Warden, electedOrAppointed, elected in many jurisdictions]
-
A.
appointedOrElected
chosen
Indicates that an entity attained a position, role, or office through either an appointment process or an electoral process.
-
B.
electedOffice
Indicates that an entity holds or has held a particular office or position as a result of an election.
-
C.
appointedBy
Indicates that one entity has been formally selected or assigned to a position, role, or office by another entity.
-
D.
appointedByOffice
Indicates that an entity attains its position or role through a formal appointment made by a specific office or official authority.
-
E.
electedWith
Indicates that one entity attained an elected position or office together with, or as part of the same electoral outcome as, 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_69a4932779b881908688590d59c71900 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49dc4f7d08190990f70b9b3af6ce5 |
completed | March 1, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69a49cf59cd0819084e67981cb371e25 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.