Triple
T25643397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Origin NS-16 crewed flight |
E642890
|
entity |
| Predicate | spaceLine |
P159789
|
FINISHED |
| Object | Blue Origin space tourism service |
—
|
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: Blue Origin space tourism service | Statement: [Blue Origin NS-16 crewed flight, spaceLine, Blue Origin space tourism service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceLine Context triple: [Blue Origin NS-16 crewed flight, spaceLine, Blue Origin space tourism service]
-
A.
pace
Indicates the rate or speed at which an action, process, or sequence progresses over time.
-
B.
spaceSegment
Indicates that one entity is a space-based component or portion of a larger system or infrastructure associated with the other entity.
-
C.
Flowline
Indicates a directed path or channel along which something (such as fluid, energy, or information) moves or is transmitted from one point to another.
-
D.
divisionLine
Indicates a boundary or separating line that divides one area, group, or portion from another.
-
E.
lineUse
Indicates how a particular line (such as a route, track, or service line) is utilized or purposed within a system or network.
- 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_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 21, 2026, 5:48 p.m.