Triple
T17141781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindustan Marut HF-24 |
E415981
|
entity |
| Predicate | combatRoleIn1971War |
P108011
|
FINISHED |
| Object | ground-attack missions |
—
|
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: ground-attack missions | Statement: [Hindustan Marut HF-24, combatRoleIn1971War, ground-attack missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatRoleIn1971War Context triple: [Hindustan Marut HF-24, combatRoleIn1971War, ground-attack missions]
-
A.
roleInWarOrConflict
chosen
Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
-
B.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
C.
roleInKoreanWar
Indicates the specific function, position, or involvement an entity had during the Korean War.
-
D.
roleInTimeWar
Indicates that an entity held a specific role or function during the period or events referred to as the Time War.
-
E.
formerMilitaryRole
Indicates that an entity previously held, but no longer holds, a specific military role or position.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2d5de10819090cbd65661b018d3 |
completed | April 18, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.