Triple
T25617317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AirLand Battle |
E642192
|
entity |
| Predicate | updatedInDoctrine |
P143224
|
FINISHED |
| Object | 1986 |
—
|
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: 1986 | Statement: [AirLand Battle, updatedInDoctrine, 1986]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updatedInDoctrine Context triple: [AirLand Battle, updatedInDoctrine, 1986]
-
A.
laterModifiedByDoctrine
chosen
Indicates that an earlier statement, rule, or decision was subsequently changed, clarified, or overridden by a later doctrinal authority or interpretation.
-
B.
replacedByDoctrine
Indicates that one doctrine has been superseded and taken its place by another doctrine.
-
C.
usesDoctrine
Indicates that one entity applies, follows, or relies on a particular doctrine in its actions or reasoning.
-
D.
statusInDoctrine
Indicates the recognized standing or role that something holds within a particular doctrinal or theological system.
-
E.
contributesToDoctrine
Indicates that one entity plays a role in forming, shaping, or supporting the doctrinal position or belief system of another entity.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5f9e8734c8190a214685b1647abe1 |
completed | May 2, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:01 p.m.