Triple
T30877081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AEHF military communications satellites |
E786506
|
entity |
| Predicate | fourthSatellite |
P171602
|
FINISHED |
| Object | AEHF-4 |
—
|
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-4 | Statement: [AEHF military communications satellites, fourthSatellite, AEHF-4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fourthSatellite Context triple: [AEHF military communications satellites, fourthSatellite, AEHF-4]
-
A.
sixthSatellite
Indicates that one entity is the sixth satellite (e.g., moon or artificial satellite) in an ordered sequence orbiting another entity.
-
B.
isFifthKnownSatelliteOf
Indicates that one object is the fifth discovered or identified natural satellite (moon) of another celestial body.
-
C.
fifthSatellite
Indicates that one entity is the fifth satellite (e.g., moon or artificial satellite) in an ordered sequence relative to another entity.
-
D.
retrievedSatellite
Indicates that an entity has successfully recovered or brought back a satellite from a prior location or state.
-
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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a1ac56b88190a820434b65c9fa23 |
completed | May 3, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 29, 2026, 8:48 p.m.