Triple
T24642085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pralay missile |
E609994
|
entity |
| Predicate | originatesFromOrganization |
P62651
|
FINISHED |
| Object | DRDO |
—
|
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: DRDO | Statement: [Pralay missile, originatesFromOrganization, DRDO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatesFromOrganization Context triple: [Pralay missile, originatesFromOrganization, DRDO]
-
A.
originalOrganization
Indicates the organization from which an entity (such as a person, document, or resource) initially originated or was first associated.
-
B.
originalOrganizationName
Indicates the name by which an organization was originally known before any renaming or rebranding.
-
C.
usesOrganization
Indicates that one entity makes use of, relies on, or operates through a particular organization to perform its functions or activities.
-
D.
endedOrganization
Indicates that an organization has ceased to exist or operate, marking the termination of its existence or activities.
-
E.
sourceOrganization
chosen
Indicates the organization from which something (such as information, a resource, or an item) originates or is provided.
- 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_69e2c4d28f848190ac38c400060e943d |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f40db2b5e08190bb55d02a4ceba306 |
completed | May 1, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d2b20881908dcc3b15cbe3e5b0 |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:33 a.m.