Triple
T25643348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NS-16 mission |
E642889
|
entity |
| Predicate | flightOutcome |
P159478
|
FINISHED |
| Object | success |
—
|
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: success | Statement: [NS-16 mission, flightOutcome, success]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightOutcome Context triple: [NS-16 mission, flightOutcome, success]
-
A.
firstFlightOutcome
Indicates the result or status of an entity’s initial flight attempt or maiden flight event.
-
B.
flightOver
Indicates that one entity moves through the air above or across another entity or area.
-
C.
flightEndedAt
Indicates the time or location at which a flight concludes or reaches its final endpoint.
-
D.
testFlight
Indicates that an aircraft or spacecraft is being flown under controlled conditions to evaluate its performance, safety, or functionality before regular use.
-
E.
performedFlightTo
Indicates that an entity (such as an aircraft or airline) carried out a flight whose destination was a specified location.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faa22e7c81908af7fe96952bebe0 |
completed | May 2, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 21, 2026, 5:48 p.m.