Triple
T37163485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emergency SOS |
E920735
|
entity |
| Predicate | satelliteVariant |
P187488
|
FINISHED |
| Object | Emergency SOS via satellite |
—
|
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: Emergency SOS via satellite | Statement: [Emergency SOS, satelliteVariant, Emergency SOS via satellite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: satelliteVariant Context triple: [Emergency SOS, satelliteVariant, Emergency SOS via satellite]
-
A.
satelliteType
Indicates that one entity is classified as a specific type or category of satellite relative to another entity.
-
B.
satellite
Indicates that one entity orbits and is gravitationally bound to another, typically larger, central body.
-
C.
retrievedSatellite
Indicates that an entity has successfully recovered or brought back a satellite from a prior location or state.
-
D.
specificCarrierVariant
Indicates that one entity is a particular, more narrowly defined version or subtype of a broader carrier entity.
-
E.
thirdSatellite
Indicates that one entity is the third satellite (in an ordered sequence of satellites) of another entity.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb55dc36d08190a0634fa680e13114 |
completed | May 6, 2026, 2:53 p.m. |
Created at: May 3, 2026, 4:15 p.m.