Triple
T28243172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz TM-32 |
E712087
|
entity |
| Predicate | spaceTourismCustomer |
P153124
|
FINISHED |
| Object | Dennis Tito |
—
|
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: Dennis Tito | Statement: [Soyuz TM-32, spaceTourismCustomer, Dennis Tito]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceTourismCustomer Context triple: [Soyuz TM-32, spaceTourismCustomer, Dennis Tito]
-
A.
spaceTourism
Indicates commercial travel or recreational trips by people to outer space or space-related environments.
-
B.
spaceAgencyCustomer
Indicates a relationship where one entity is a customer that purchases or contracts services from a space agency.
-
C.
spaceTouristNumber
Indicates the number of space tourists associated with or involved in a particular spaceflight, mission, or context.
-
D.
spaceflightParticipant
chosen
Indicates that an entity takes part in a spaceflight mission, typically as a non-professional or guest participant rather than as career crew.
-
E.
spaceflightOperator
Indicates that an entity operates, manages, or is responsible for conducting spaceflight missions or services.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 10:59 p.m.