Triple
T25643217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wally Funk |
E642886
|
entity |
| Predicate | spaceflightOperator |
P158954
|
FINISHED |
| Object | Blue Origin |
—
|
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: Blue Origin | Statement: [Wally Funk, spaceflightOperator, Blue Origin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceflightOperator Context triple: [Wally Funk, spaceflightOperator, Blue Origin]
-
A.
spaceflightType
Indicates the specific category or mode of spaceflight associated with an entity, such as orbital, suborbital, interplanetary, or other mission types.
-
B.
spaceAgencyCustomer
Indicates a relationship where one entity is a customer that purchases or contracts services from a space agency.
-
C.
spaceTourism
Indicates commercial travel or recreational trips by people to outer space or space-related environments.
-
D.
spaceflightParticipant
Indicates that an entity takes part in a spaceflight mission, typically as a non-professional or guest participant rather than as career crew.
-
E.
spaceAgency
Indicates that one entity is a space agency that operates, manages, or oversees space-related missions, programs, or activities on behalf of the other entity.
- 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_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 5:48 p.m.