Triple
T4120693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western theatre of the Indian Army |
E92603
|
entity |
| Predicate | planningLevel |
P33672
|
FINISHED |
| Object | operational level |
—
|
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: operational level | Statement: [Western theatre of the Indian Army, planningLevel, operational level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planningLevel Context triple: [Western theatre of the Indian Army, planningLevel, operational level]
-
A.
hasPlanningLevel
chosen
Indicates that an entity is associated with a specific stage, tier, or granularity within a planning or scheduling hierarchy.
-
B.
planningPriority
Indicates the relative importance or urgency assigned to an item, task, or objective when organizing or scheduling plans.
-
C.
decisionMakingLevel
Indicates the degree or hierarchy of authority an entity has in making decisions within a given context.
-
D.
hasPlanningStatus
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
-
E.
policyLevel
Indicates the degree or tier of strictness, scope, or priority associated with a given policy.
- 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_69aed9685f70819086932777aec8d959 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69af0246e40081908ad6741a830ca68e |
completed | March 9, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69af01867698819098e4144634b2ec4f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:41 p.m.