Triple
T25617316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AirLand Battle |
E642192
|
entity |
| Predicate | introducedInDoctrine |
P81190
|
FINISHED |
| Object | 1982 |
—
|
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: 1982 | Statement: [AirLand Battle, introducedInDoctrine, 1982]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedInDoctrine Context triple: [AirLand Battle, introducedInDoctrine, 1982]
-
A.
definedDoctrineAt
chosen
Indicates that a particular doctrine was formally established, articulated, or codified at a specific place or time.
-
B.
currentDoctrine
Indicates the doctrine, policy, or set of guiding principles that is presently in force or officially adopted at a given time.
-
C.
containsDoctrine
Indicates that one entity includes, embodies, or incorporates the doctrine, principles, or teachings represented by another entity.
-
D.
citedForDoctrine
Indicates that one entity is cited as an authoritative source or precedent for a particular doctrine, principle, or rule in relation to another entity.
-
E.
developedDoctrine
Indicates that one entity created, formulated, or significantly advanced a particular doctrine or set of principles.
- 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_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 21, 2026, 5:01 p.m.