Triple

T23844806
Position Surface form Disambiguated ID Type / Status
Subject Surya ICBM project E591089 entity
Predicate publicInformationStatus P154163 FINISHED
Object not officially acknowledged 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: not officially acknowledged | Statement: [Surya ICBM project, publicInformationStatus, not officially acknowledged]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: publicInformationStatus
Context triple: [Surya ICBM project, publicInformationStatus, not officially acknowledged]
  • A. exportStatus
    Indicates the current state or outcome of an entity’s export process (e.g., pending, in progress, completed, or failed).
  • B. customStatus
    Indicates that an entity has a user-defined or non-standard status assigned to it.
  • C. notableInformationStatus
    Indicates that there exists noteworthy or significant information about an entity and specifies the status or condition of that information (e.g., confirmed, unverified, disputed, or missing).
  • D. publicProfile
    Indicates that an entity’s profile or identifying information is visible and accessible to the general public.
  • E. actualStatus
    Indicates the current, real-world state or condition of an entity, as opposed to a planned, expected, or nominal status.
  • 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.