Triple
T21999465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Army 15 Corps |
E543286
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | XV Corps |
—
|
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: XV Corps | Statement: [Indian Army 15 Corps, alsoKnownAs, XV Corps]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: XV Corps Context triple: [Indian Army 15 Corps, alsoKnownAs, XV Corps]
-
A.
XV Corps
chosen
XV Corps is a key field formation of the Indian Army responsible for military operations and security in the Kashmir region.
-
B.
XV Corps
XV Corps was a field corps of the Ottoman Army that served as a major combat formation during World War I.
-
C.
XII Corps
XII Corps is a major field formation of the Pakistan Army responsible for operations and defense primarily in the Balochistan region.
-
D.
XII Corps
XII Corps is a field formation of the Indian Army responsible for operations and defense in parts of western India, including sectors along the border with Pakistan.
-
E.
XII Corps
XII Corps was a major French military formation of the Napoleonic Wars, composed largely of allied contingents and active in several key campaigns in Central Europe.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12768c0088190b0c8d5cd9b7bf710 |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 16, 2026, 8:19 p.m.