Triple
T33130932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GSAT-14 |
E847865
|
entity |
| Predicate | transponders |
P96034
|
FINISHED |
| Object | Ku-band transponders |
—
|
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: Ku-band transponders | Statement: [GSAT-14, transponders, Ku-band transponders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transponders Context triple: [GSAT-14, transponders, Ku-band transponders]
-
A.
numberOfTransponders
Indicates the quantity of transponders associated with or contained by a given entity.
-
B.
hasTransponders
Indicates that one entity possesses, is equipped with, or includes one or more transponders in relation to another entity or context.
-
C.
transponderType
chosen
Indicates the specific kind or category of transponder associated with an entity or used in a given context.
-
D.
requiresTransponder
Indicates that one entity must have or use a transponder in order to interact with, access, or be accepted by another entity or system.
-
E.
transmitterType
Indicates the kind or category of transmitter associated with or used by an entity.
- 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
Created at: May 1, 2026, 1:27 a.m.