Triple
T27340020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Poyer |
E690069
|
entity |
| Predicate | selectionForExecution |
P381
|
FINISHED |
| Object | chosen by lot among rebel leaders |
—
|
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: chosen by lot among rebel leaders | Statement: [John Poyer, selectionForExecution, chosen by lot among rebel leaders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionForExecution Context triple: [John Poyer, selectionForExecution, chosen by lot among rebel leaders]
-
A.
selectionFrom
Indicates that one entity is chosen as a member or subset from a larger set or collection represented by another entity.
-
B.
runtimeSelection
Indicates that something is chosen or determined dynamically during execution time rather than fixed in advance.
-
C.
selectedTo
Indicates that one entity has been chosen or designated from a set of candidates to perform a role, receive something, or participate in an activity in relation to another entity.
-
D.
selectionMadeBy
chosen
Indicates that a particular choice or selection was performed or decided by a specific agent or entity.
-
E.
selectionProcess
Indicates the procedure or set of steps by which one or more options are evaluated and chosen from a larger set of candidates.
- 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_69ef355e5b388190a8fc1eba9b4a6656 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 11:42 a.m.