Triple
T531296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnatic region of India |
E12227
|
entity |
| Predicate | wasTheaterOf |
P687
|
FINISHED |
| Object | Anglo-French rivalry in India |
—
|
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: Anglo-French rivalry in India | Statement: [Carnatic region of India, wasTheaterOf, Anglo-French rivalry in India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasTheaterOf Context triple: [Carnatic region of India, wasTheaterOf, Anglo-French rivalry in India]
-
A.
theater
Indicates that an entity is a theater or is functioning in the role of a theater (a venue where performances or films are shown).
-
B.
theaterOfWar
chosen
Indicates that a specified location or region is the primary area where a particular conflict, war, or military operation takes place.
-
C.
notableTheater
Indicates that there is a significant or well-known theater associated with the subject.
-
D.
theatricalSetting
Indicates the spatial or contextual environment in which a theatrical performance or dramatic action takes place.
-
E.
primaryTheater
Indicates that a particular location or region is the main setting or principal area where an event, activity, or operation takes place.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b257108190a537dffbb9d621b5 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.