Triple
T31902931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Rajiv |
E814471
|
entity |
| Predicate | controlledByAfterOperation |
P21851
|
FINISHED |
| Object | Indian Army |
—
|
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: Indian Army | Statement: [Operation Rajiv, controlledByAfterOperation, Indian Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledByAfterOperation Context triple: [Operation Rajiv, controlledByAfterOperation, Indian Army]
-
A.
controlledAfter
chosen
Indicates that one entity gains or maintains control over another entity only after a specified time, event, or condition has occurred.
-
B.
controlledByAtEnd
Indicates that one entity has control or governing authority over another entity at the final point or conclusion of a specified process, period, or event.
-
C.
operatedAfter
Indicates that one operation or action occurred later in time than another specified operation or action.
-
D.
operatorAfterConsolidation
Indicates that one operator entity succeeds or replaces another operator entity after a consolidation event (such as a merger or acquisition).
-
E.
laterOperatedOn
Indicates that one entity is subjected to an operation or procedure at a time subsequent to another referenced event or action.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: May 1, 2026, midnight