Triple
T36670053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRNSS-1C |
E905385
|
entity |
| Predicate | spaceSegmentOf |
P70063
|
FINISHED |
| Object | NavIC |
—
|
NE NERFINISHED |
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: NavIC | Statement: [IRNSS-1C, spaceSegmentOf, NavIC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceSegmentOf Context triple: [IRNSS-1C, spaceSegmentOf, NavIC]
-
A.
spaceSegment
chosen
Indicates that one entity is a space-based component or portion of a larger system or infrastructure associated with the other entity.
-
B.
spaceDependence
Indicates a relationship where one entity’s properties, behavior, or validity depend on spatial position or configuration relative to another entity or reference frame.
-
C.
locatedInSpace
Indicates that one entity exists or is positioned within a specific region or area of physical space relative to another.
-
D.
hostSpaceAgency
Indicates that one entity serves as the space agency that organizes, manages, or officially represents space-related activities for another entity (such as a mission, event, or facility).
-
E.
spaceAgencyCustomer
Indicates a relationship where one entity is a customer that purchases or contracts services from a space agency.
- 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:12 p.m.