Triple
T23844814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surya ICBM project |
E591089
|
entity |
| Predicate | rangeDescription |
P154164
|
FINISHED |
| Object | capable of transcontinental strikes |
—
|
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: capable of transcontinental strikes | Statement: [Surya ICBM project, rangeDescription, capable of transcontinental strikes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeDescription Context triple: [Surya ICBM project, rangeDescription, capable of transcontinental strikes]
-
A.
range
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
-
B.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
C.
rangeVariant
Indicates that one entity is a variant or alternative form within the value range defined or covered by another entity.
-
D.
rangeType
Indicates the type or category of values that can appear in the range (output) position of a property or relation.
-
E.
rangeRestricted
Indicates that the relationship or action applies only within a specified, limited subset of a broader domain or scope.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:09 p.m.