Triple
T6369111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DRDO Netra AEW&CS |
E143301
|
entity |
| Predicate | missionSystem |
P15789
|
FINISHED |
| Object | indigenous mission computer |
—
|
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: indigenous mission computer | Statement: [DRDO Netra AEW&CS, missionSystem, indigenous mission computer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionSystem Context triple: [DRDO Netra AEW&CS, missionSystem, indigenous mission computer]
-
A.
militarySystem
chosen
Indicates a relationship where an entity functions as, belongs to, or is characterized by a particular military organizational or operational system.
-
B.
missionField
Indicates a relationship where an entity’s work, activity, or purpose is directed toward a particular area, domain, or target context as its mission focus.
-
C.
missionCadence
Indicates the frequency or regular interval at which missions are planned, launched, or conducted.
-
D.
missionAssociation
Indicates a relationship where an entity is connected to, involved in, or associated with a particular mission or organized endeavor.
-
E.
mission
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
- 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_69c008d8c61081908bcaf61510d881ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c068265a7481908571be7ea4ac11b7 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:33 p.m.