Triple
T10846025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaganyaan test missions |
E256010
|
entity |
| Predicate | technologyTested |
P60540
|
FINISHED |
| Object | Crew Module |
—
|
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: Crew Module | Statement: [Gaganyaan test missions, technologyTested, Crew Module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyTested Context triple: [Gaganyaan test missions, technologyTested, Crew Module]
-
A.
testedDevice
Indicates that one entity has performed a test on, or experimentally evaluated, another entity as a device.
-
B.
technologyPresent
Indicates that a particular technology exists, is available, or is currently in use in the given context or situation.
-
C.
testedOn
chosen
Indicates that an entity has been used as the subject or material in a test, experiment, or evaluation performed by another entity.
-
D.
technologyDiscussed
Indicates that a conversation, text, or interaction includes discussion or mention of a particular technology.
-
E.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d750d132e081909c977b3dc4110ca4 |
completed | April 9, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d70d2b51448190bae748ed6c23edde |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.