Triple
T25516067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Militia (United Kingdom) |
E639510
|
entity |
| Predicate | embodimentCondition |
P158616
|
FINISHED |
| Object | war |
—
|
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: war | Statement: [Militia (United Kingdom), embodimentCondition, war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: embodimentCondition Context triple: [Militia (United Kingdom), embodimentCondition, war]
-
A.
obligationCondition
Indicates that one situation or state serves as the condition under which an obligation for an entity becomes active or must be fulfilled.
-
B.
eligibleBody
Indicates that an entity qualifies as an appropriate or permitted body (e.g., organization or institution) to participate in or be subject to a specified relationship or action.
-
C.
featuresCondition
Indicates that an entity includes, exhibits, or is characterized by a particular condition.
-
D.
presentCondition
Indicates that an entity currently has or exhibits a particular state, situation, or condition.
-
E.
containsCondition
Indicates that one entity includes, embodies, or is associated with a particular condition.
- 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f832d48c8190984c9370816aaf94 |
completed | May 2, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 2:56 p.m.