Triple

T11146124
Position Surface form Disambiguated ID Type / Status
Subject Indian Remote Sensing satellite series E263673 entity
Predicate typicalOrbitType P7214 FINISHED
Object Sun-synchronous orbit 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: Sun-synchronous orbit | Statement: [Indian Remote Sensing satellite series, typicalOrbitType, Sun-synchronous orbit]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalOrbitType
Context triple: [Indian Remote Sensing satellite series, typicalOrbitType, Sun-synchronous orbit]
  • A. orbitType chosen
    Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
  • B. designedForOrbitType
    Indicates that something is specifically created or configured to operate within a particular type or class of orbit.
  • C. isOrbital
    Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
  • D. orbitalBodyType
    Indicates the classification of an orbital body in terms of its type (e.g., planet, moon, asteroid, comet) within an orbital system.
  • E. orbits
    Indicates that one object moves in a curved, usually repetitive path around another object due to a central force such as gravity.
  • 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_69d6aa9ccddc8190868998c8b7beb060 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e86e9ef48190b4df4b14319a954f completed April 9, 2026, 5:57 p.m.
PD Predicate disambiguation batch_69d75ce104908190b6cc31ef2f67846a completed April 9, 2026, 8:01 a.m.
Created at: April 8, 2026, 9:28 p.m.