Triple
T4120675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western theatre of the Indian Army |
E92603
|
entity |
| Predicate | theatreDirection |
P33209
|
FINISHED |
| Object | western |
—
|
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: western | Statement: [Western theatre of the Indian Army, theatreDirection, western]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: theatreDirection Context triple: [Western theatre of the Indian Army, theatreDirection, western]
-
A.
theatreOf
chosen
Indicates that an event, action, or operation takes place within or is primarily associated with a particular theatre or venue.
-
B.
theatre
Indicates that an entity is a theater or is associated with theatrical performances or activities.
-
C.
theatricalContext
Indicates the situational or environmental circumstances related to a theatrical performance or production in which an action or relationship occurs.
-
D.
theatricalSetting
Indicates the spatial or contextual environment in which a theatrical performance or dramatic action takes place.
-
E.
theaterWork
Indicates a relationship where an entity is a theatrical work (such as a play or stage production) associated with another entity, typically as its subject, creator, or context.
- 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.