Triple
T2808309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hutterites |
E54105
|
entity |
| Predicate | avoidanceOf |
P22417
|
FINISHED |
| Object | military service |
—
|
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: military service | Statement: [Hutterites, avoidanceOf, military service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: avoidanceOf Context triple: [Hutterites, avoidanceOf, military service]
-
A.
designedToAvoid
Indicates that something was intentionally created or configured in a way that prevents or minimizes a particular outcome, condition, or interaction.
-
B.
triedToAvoid
chosen
Indicates an entity made an effort or took action to prevent contact with, involvement in, or the occurrence of another entity or situation.
-
C.
avoidsRoute
Indicates that an entity deliberately does not use or travel along a particular route.
-
D.
prevented
Indicates that one entity stopped, hindered, or made it impossible for another entity or event to occur or proceed.
-
E.
abandonment
Indicates the act of one party leaving, forsaking, or giving up responsibility for another party or thing.
- 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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde2fdcf88190a52e515c166ea8f7 |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd059f308190853191f6ffe2bc6f |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.