Triple
T7218947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Bailey |
E150206
|
entity |
| Predicate | roleDuringBlackHawkWar |
P75515
|
FINISHED |
| Object | militia leader |
—
|
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: militia leader | Statement: [David Bailey, roleDuringBlackHawkWar, militia leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleDuringBlackHawkWar Context triple: [David Bailey, roleDuringBlackHawkWar, militia leader]
-
A.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
roleInAH64
Indicates that an entity has a specific functional role or position in relation to the AH-64 attack helicopter.
-
C.
formerMilitaryRole
Indicates that an entity previously held, but no longer holds, a specific military role or position.
-
D.
roleAfterWar
Indicates the role or position an entity assumes following the end of a war or armed conflict.
-
E.
roleInMissions
Indicates the specific function, duty, or position an entity holds within one or more missions.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9b045c48190b27b2d6f7c11026f |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e75f84e481909e7866186ae80cff |
completed | March 27, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69c6e889854481908c765ce2107f2d3a |
completed | March 27, 2026, 8:28 p.m. |
Created at: March 27, 2026, 2:53 p.m.