Triple
T2523637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durham County Manager |
E55580
|
entity |
| Predicate | appointedRole |
P8553
|
FINISHED |
| Object | not elected by popular vote |
—
|
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: not elected by popular vote | Statement: [Durham County Manager, appointedRole, not elected by popular vote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedRole Context triple: [Durham County Manager, appointedRole, not elected by popular vote]
-
A.
appointedAs
chosen
Indicates that one entity is formally assigned or designated to hold a specific role, position, or title in relation to another entity.
-
B.
appointedFrom
Indicates that an entity was selected or assigned to a position or role originating from a specified source, body, or prior position.
-
C.
appointedFor
Indicates that an entity has been officially assigned or designated to perform a specific role, task, or function for another entity or purpose.
-
D.
appointed
Indicates that one entity formally assigns another entity to a position, role, or responsibility.
-
E.
assignsRoleTo
Indicates that one entity designates or grants a specific role or position to 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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd23a0a548190b44393e0f823f7a9 |
completed | March 7, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69abd0c144b0819092f32a13c1d127e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.