Triple
T21123432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hot Bird 6 |
E520489
|
entity |
| Predicate | locatedInOrbitArc |
P50050
|
FINISHED |
| Object | Hot Bird orbital slot at 13°E |
—
|
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: Hot Bird orbital slot at 13°E | Statement: [Hot Bird 6, locatedInOrbitArc, Hot Bird orbital slot at 13°E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInOrbitArc Context triple: [Hot Bird 6, locatedInOrbitArc, Hot Bird orbital slot at 13°E]
-
A.
locatedInOrbitAbove
Indicates that one entity is positioned in an orbital path around and above another entity.
-
B.
includesOrbitOf
Indicates that one entity’s orbital path or region fully contains or encompasses the orbital path or region of another entity.
-
C.
isOnOrbital
chosen
Indicates that one entity is located on or traveling along the orbital path associated with another entity.
-
D.
onOrbitalRoute
Indicates that one object is currently traveling along or positioned on a defined orbital path around another body.
-
E.
isOrbitalRouteFor
Indicates that one path or trajectory serves as the designated orbital route followed by another object (such as a spacecraft or satellite).
- 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72236b2d88190bef9f0cd6924ca92 |
completed | April 21, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:55 p.m.