Triple
T38169242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Yah 2 |
E1000021
|
entity |
| Predicate | locatedInGeostationarySlot |
P207626
|
FINISHED |
| Object | about 49 degrees East longitude |
—
|
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: about 49 degrees East longitude | Statement: [Al Yah 2, locatedInGeostationarySlot, about 49 degrees East longitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInGeostationarySlot Context triple: [Al Yah 2, locatedInGeostationarySlot, about 49 degrees East longitude]
-
A.
locatedInOrbitAbove
Indicates that one entity is positioned in an orbital path around and above another entity.
-
B.
TDRSSOrbitalSlot
Indicates the specific orbital position or slot assigned to an object within the Tracking and Data Relay Satellite System (TDRSS) constellation.
-
C.
numberOfGeostationarySatellites
Indicates the quantity of geostationary satellites associated with a given entity.
-
D.
comparedToGeostationaryOrbit
Indicates a comparison between an entity and a geostationary orbit in terms of position, altitude, or orbital characteristics.
-
E.
deployedSatellite
Indicates that one entity has placed another entity into orbit or operational status as a satellite.
- 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_69f76daaace48190a38cee37f8ce343f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037df009f4819082e04683e6e8a106 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:29 p.m.