Triple
T19368076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telstar 3C |
E484455
|
entity |
| Predicate | hasTransponders |
P135675
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Telstar 3C, hasTransponders, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransponders Context triple: [Telstar 3C, hasTransponders, yes]
-
A.
numberOfTransponders
Indicates the quantity of transponders associated with or contained by a given entity.
-
B.
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.
-
C.
transponderType
Indicates the specific kind or category of transponder associated with an entity or used in a given context.
-
D.
hasFMTransmitter
Indicates that one entity is equipped with or includes an FM radio transmitter component or capability.
-
E.
hasTransmissionNetwork
Indicates that one entity is connected to or served by a particular transmission network through which something (such as electricity, data, or signals) is conveyed.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e619adac8881909136c50351f3683d |
completed | April 20, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:35 p.m.