Triple
T16222117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tigris Front |
E393753
|
entity |
| Predicate | militaryTheatreType |
P1403
|
FINISHED |
| Object | land warfare |
—
|
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: land warfare | Statement: [Tigris Front, militaryTheatreType, land warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryTheatreType Context triple: [Tigris Front, militaryTheatreType, land warfare]
-
A.
militaryTheater
Indicates that an entity is a geographic or operational area where military operations or campaigns are conducted.
-
B.
militaryTheaterCovered
Indicates that a specified military theater or area of operations falls within the geographic or operational scope covered by another entity (such as a plan, command, or agreement).
-
C.
theaterOfWar
Indicates that a specified location or region is the primary area where a particular conflict, war, or military operation takes place.
-
D.
warfareType
chosen
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
-
E.
fieldOfOperation
Indicates the domain, area, or scope within which an entity operates or carries out its primary 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e227fcf058819099d5ff965cc2c267 |
completed | April 17, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.