Triple
T4053416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Essay on the Ballot |
E84637
|
entity |
| Predicate | positionHeldInWork |
P5188
|
FINISHED |
| Object | advocacy of secret voting |
—
|
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: advocacy of secret voting | Statement: [Essay on the Ballot, positionHeldInWork, advocacy of secret voting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionHeldInWork Context triple: [Essay on the Ballot, positionHeldInWork, advocacy of secret voting]
-
A.
positionInWork
chosen
Indicates the specific role, rank, or placement an entity holds within a larger work or structured composition.
-
B.
positionHeld
Indicates that an entity occupies or has occupied a specific role, job, office, or position within an organization or context.
-
C.
workPosition
Indicates the specific job role or position that an entity holds within an organization or workplace.
-
D.
officePreviouslyHeldBy
Indicates that a particular office or position was formerly occupied by a specified person or entity.
-
E.
locationOfWork
Indicates the place or site where an entity performs its work or carries out its professional activities.
- 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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefba878a48190a2e234d775215938 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef90249e4819095e9e043bc4aa9a6 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:37 p.m.