Triple
T16124453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Everson |
E391230
|
entity |
| Predicate | wasConscientiousObjector |
P121564
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [William Everson, wasConscientiousObjector, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasConscientiousObjector Context triple: [William Everson, wasConscientiousObjector, true]
-
A.
hadMilitaryObligationsTo
Indicates that one party was bound by duty or law to provide military service, support, or protection to another party.
-
B.
volunteerOrConscript
Indicates that an entity participates in a role, service, or activity either by choosing to do so voluntarily or by being compelled or drafted into it.
-
C.
usesConscription
Indicates that a state or authority compels individuals into military or national service through mandatory conscription.
-
D.
isVeteranOf
Indicates that an entity has previously served in and been discharged from a specified military conflict, campaign, or armed force.
-
E.
personReferredToMilitaryService
Indicates that one person has directed, recommended, or assigned another person to perform military service.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2020408a88190bf3dfc893d577c55 |
completed | April 17, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e183b9d3f08190953ada68f4272996 |
completed | April 17, 2026, 12:50 a.m. |
Created at: April 10, 2026, 5 a.m.