Triple
T25513050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FM 3-24/MCWP 3-33.5 |
E639432
|
entity |
| Predicate | theaterApplication |
P1401
|
FINISHED |
| Object | War in Afghanistan (2001–2021) |
—
|
NE NERFINISHED |
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 in Afghanistan (2001–2021) | Statement: [FM 3-24/MCWP 3-33.5, theaterApplication, War in Afghanistan (2001–2021)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: theaterApplication Context triple: [FM 3-24/MCWP 3-33.5, theaterApplication, War in Afghanistan (2001–2021)]
-
A.
theatreCity
Indicates that a theatre is located in, or primarily associated with, a particular city.
-
B.
appliesToTheater
Indicates that something is relevant or applicable specifically to a theater or theatrical context.
-
C.
appliedToTheater
Indicates that an application, request, or action has been directed toward or submitted to a specific theater.
-
D.
theaterCommander
chosen
Indicates that an entity serves as the commanding authority over military operations within a specific theater or area of operations.
-
E.
theaterSupport
Indicates that one entity provides assistance, resources, or services to support another entity in the context of theater or theatrical activities.
- 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f82fe30881909915c13a183be6c3 |
completed | May 2, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 2:53 p.m.