Triple
T28243171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz TM-32 |
E712087
|
entity |
| Predicate | spaceTourismMilestone |
P74623
|
FINISHED |
| Object | carried first fee-paying space tourist |
—
|
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: carried first fee-paying space tourist | Statement: [Soyuz TM-32, spaceTourismMilestone, carried first fee-paying space tourist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceTourismMilestone Context triple: [Soyuz TM-32, spaceTourismMilestone, carried first fee-paying space tourist]
-
A.
spaceTourism
chosen
Indicates commercial travel or recreational trips by people to outer space or space-related environments.
-
B.
spaceTouristNumber
Indicates the number of space tourists associated with or involved in a particular spaceflight, mission, or context.
-
C.
spaceMissionsFlown
Indicates the number or specific instances of space missions that an entity has participated in or carried out.
-
D.
spaceflightDate
Indicates the date on which a spaceflight event occurs or is scheduled to occur.
-
E.
spaceAgencyCustomer
Indicates a relationship where one entity is a customer that purchases or contracts services from a space agency.
- 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_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 10:59 p.m.