Triple
T19753101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSP-16 |
E474431
|
entity |
| Predicate | monitorsFrom |
P58575
|
FINISHED |
| Object | geostationary orbit |
—
|
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: geostationary orbit | Statement: [DSP-16, monitorsFrom, geostationary orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monitorsFrom Context triple: [DSP-16, monitorsFrom, geostationary orbit]
-
A.
monitors
Indicates that one entity observes, tracks, or checks the state, behavior, or performance of another entity over time.
-
B.
monitorsMedium
Indicates that one entity observes, tracks, or supervises the state or activity of a particular medium (such as a channel, platform, or communication medium).
-
C.
monitoredFor
Indicates that one entity is being observed or tracked over time to detect, assess, or manage the occurrence or progression of another entity (such as a condition, event, or risk).
-
D.
typicalMonitor
Indicates that one entity commonly or characteristically monitors, observes, or oversees another entity in a usual or expected manner.
-
E.
observesFrom
chosen
Indicates that one entity watches, monitors, or takes note of another entity from a particular vantage point or location.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6529cae048190b4f8e6ba409bcf8e |
completed | April 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.