Triple
T3519145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senior Warden |
E74376
|
entity |
| Predicate | succeedsFromOffice |
P48494
|
FINISHED |
| Object | Junior Warden 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: Junior Warden in many jurisdictions | Statement: [Senior Warden, succeedsFromOffice, Junior Warden in many jurisdictions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeedsFromOffice Context triple: [Senior Warden, succeedsFromOffice, Junior Warden in many jurisdictions]
-
A.
succeededInOffice
Indicates that one officeholder directly followed another in holding the same official position.
-
B.
successorOfficeEstablished
Indicates that a new office or position was formally created to replace or succeed a previous one.
-
C.
successorOfficeTo
Indicates that one office or position directly follows and replaces another in an official sequence or hierarchy.
-
D.
successorOfficeHolder
Indicates that one office holder directly follows another in occupying the same official position.
-
E.
officeHolderBecame
Indicates that an individual assumed or transitioned into holding a particular office or official position.
- 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_69ad85cfb5c881909c9a2edd9d6043cc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc49dea88190924c8abd29aabdad |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae10689c8190b7dc6d7daa8295b6 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed74ecc8190b74dc70ab59a3e1c |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:19 p.m.