Triple
T135729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOFIA airborne observatory operations |
E2740
|
entity |
| Predicate | succeeds |
P78
|
FINISHED |
| Object | Kuiper Airborne Observatory operations |
—
|
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: Kuiper Airborne Observatory operations | Statement: [SOFIA airborne observatory operations, succeeds, Kuiper Airborne Observatory operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeeds Context triple: [SOFIA airborne observatory operations, succeeds, Kuiper Airborne Observatory operations]
-
A.
successor
chosen
Indicates that one entity directly follows another in an ordered sequence or position.
-
B.
satisfies
Indicates that one entity meets, fulfills, or complies with the requirements, conditions, or expectations specified by another.
-
C.
passes
Indicates that one entity successfully transfers, hands over, or moves something (such as an object, message, or responsibility) to another entity.
-
D.
achieved
Indicates that an entity successfully reached, obtained, or accomplished a specified goal, result, or state.
-
E.
approves
Indicates that one entity formally accepts, authorizes, or agrees to a proposal, action, or decision made by another entity.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257a4edf081908c494c8370c76b9a |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a25651b9048190a6277b7fec98c1ea |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.