Triple
T23250740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astra 19.2°E |
E581723
|
entity |
| Predicate | typicalReceptionEquipment |
P101141
|
FINISHED |
| Object | small satellite dish |
—
|
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: small satellite dish | Statement: [Astra 19.2°E, typicalReceptionEquipment, small satellite dish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalReceptionEquipment Context triple: [Astra 19.2°E, typicalReceptionEquipment, small satellite dish]
-
A.
typicalEquipmentPowered
Indicates that one entity is commonly powered or operated by another entity as its usual source of power.
-
B.
typeOfEquipmentUsed
chosen
Indicates that a particular piece or category of equipment is utilized in performing a specific action, process, or activity.
-
C.
typicalEquipmentLevel
Indicates the usual or standard amount or quality of equipment associated with an entity or situation.
-
D.
typicalServerDevice
Indicates that the subject is a device that is commonly or characteristically used as a server in typical scenarios.
-
E.
supportedEquipment
Indicates that one entity provides compatibility with, or operational support for, a specified piece of equipment.
- 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_69e24606b17c81908aba1a4911c8a8ba |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f193f5aa9081909775fb7f7dc660b3 |
completed | April 29, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:10 p.m.