Triple
T15829820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medium Explorer |
E383839
|
entity |
| Predicate | includesMissionType |
P17730
|
FINISHED |
| Object | observatory-class satellites |
—
|
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: observatory-class satellites | Statement: [Medium Explorer, includesMissionType, observatory-class satellites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesMissionType Context triple: [Medium Explorer, includesMissionType, observatory-class satellites]
-
A.
exampleMission
Indicates that one entity serves as a representative or illustrative mission associated with another entity.
-
B.
supportsMissionType
chosen
Indicates that one entity is capable of handling, enabling, or being compatible with a specified type of mission.
-
C.
typeOfMission
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
D.
capturesMissionOf
Indicates that one entity records, represents, or encapsulates the mission or overarching purpose of another entity.
-
E.
hasMissionSystem
Indicates that an entity is equipped with or associated with a specific mission-related system or subsystem.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e636bb48190a6b39feb550aaa3d |
completed | April 16, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.