Triple
T26530032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plasma Diagnostics Package |
E670793
|
entity |
| Predicate | wasFlownOn |
P76485
|
FINISHED |
| Object | Space Shuttle Challenger |
—
|
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: Space Shuttle Challenger | Statement: [Plasma Diagnostics Package, wasFlownOn, Space Shuttle Challenger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFlownOn Context triple: [Plasma Diagnostics Package, wasFlownOn, Space Shuttle Challenger]
-
A.
isFlownOn
chosen
Indicates that an entity (such as a person or object) travels or is transported using a particular aircraft or airline as the means of flight.
-
B.
isFlownWith
Indicates that one entity travels by air together with, or using the same flight as, another entity.
-
C.
officiallyFlownOn
Indicates that something has been formally carried or transported aboard a specific flight or aircraft under official or authorized status.
-
D.
flownWith
Indicates that two entities have traveled together on the same flight or aircraft.
-
E.
ownsAirline
Indicates that one entity has legal ownership or controlling interest in an airline company.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613f5ec28819099ec679f636d61d9 |
completed | May 2, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:34 a.m.