Triple
T30877080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AEHF military communications satellites |
E786506
|
entity |
| Predicate | thirdSatellite |
P182770
|
FINISHED |
| Object | AEHF-3 |
—
|
NE NERFINISHED |
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: AEHF-3 | Statement: [AEHF military communications satellites, thirdSatellite, AEHF-3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdSatellite Context triple: [AEHF military communications satellites, thirdSatellite, AEHF-3]
-
A.
fourthSatellite
Indicates that one entity is the fourth satellite (e.g., moon or artificial satellite) in an ordered sequence orbiting another entity.
-
B.
sixthSatellite
Indicates that one entity is the sixth satellite (e.g., moon or artificial satellite) in an ordered sequence orbiting another entity.
-
C.
satellite
Indicates that one entity orbits and is gravitationally bound to another, typically larger, central body.
-
D.
retrievedSatellite
Indicates that an entity has successfully recovered or brought back a satellite from a prior location or state.
-
E.
isFifthKnownSatelliteOf
Indicates that one object is the fifth discovered or identified natural satellite (moon) of another celestial body.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7908ec35881909a42f954fb9fa16e |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78fd3fd888190b7db0b563f298585 |
completed | May 3, 2026, 6:11 p.m. |
Created at: April 29, 2026, 8:48 p.m.