Triple
T23844801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surya ICBM project |
E591089
|
entity |
| Predicate | allegedRangeCategory |
P154162
|
FINISHED |
| Object | intercontinental |
—
|
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: intercontinental | Statement: [Surya ICBM project, allegedRangeCategory, intercontinental]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedRangeCategory Context triple: [Surya ICBM project, allegedRangeCategory, intercontinental]
-
A.
hasRangeCategory
Indicates that a property or measurement falls within a specified category or interval of possible values.
-
B.
categoryRange
Indicates that a category or classification spans from a defined lower bound to an upper bound within a specified range.
-
C.
majorRangeIncludes
Indicates that a major range (such as a primary geographic or categorical span) encompasses or contains another specified range.
-
D.
allegedUse
Indicates that something is claimed or suspected to have been used, without confirming that the use actually occurred.
-
E.
allegedTargetGroup
Indicates that a group is claimed or suspected to be the intended target of an action, plan, or attack, without confirming that the claim is true.
- 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.