Triple
T23844799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surya ICBM project |
E591089
|
entity |
| Predicate | allegedPurpose |
P50822
|
FINISHED |
| Object | development of an intercontinental ballistic missile |
—
|
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: development of an intercontinental ballistic missile | Statement: [Surya ICBM project, allegedPurpose, development of an intercontinental ballistic missile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedPurpose Context triple: [Surya ICBM project, allegedPurpose, development of an intercontinental ballistic missile]
-
A.
allegedUse
Indicates that something is claimed or suspected to have been used, without confirming that the use actually occurred.
-
B.
allegedGoal
chosen
Indicates that one entity is claimed or reported to have the goal or intended objective of another entity, without asserting that the goal is actually true.
-
C.
hasEstablishedPurpose
Indicates that an entity has a defined and recognized purpose or intended function already determined.
-
D.
operationalPurpose
Indicates the function, role, or intended use that an entity is designed or configured to perform in an operational context.
-
E.
accessPurpose
Indicates that one entity uses or accesses another entity specifically for a defined purpose or intended use.
- 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c88a4b948190989a261e79b996a6 |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:09 p.m.