Triple
T27549032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 8 |
E695440
|
entity |
| Predicate | landingVehicle |
P37567
|
FINISHED |
| Object | Soyuz TMA-3 |
—
|
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: Soyuz TMA-3 | Statement: [Expedition 8, landingVehicle, Soyuz TMA-3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingVehicle Context triple: [Expedition 8, landingVehicle, Soyuz TMA-3]
-
A.
landingSiteVehicle
Indicates that a vehicle uses or is assigned to a particular location as its landing site.
-
B.
reentryVehicle
chosen
Indicates that an entity functions as a vehicle designed to re-enter an atmosphere from space.
-
C.
landingCapability
Indicates the ability or suitability of an entity (e.g., a vehicle or system) to perform a landing under specified conditions.
-
D.
hasLandingSystem
Indicates that an entity is equipped with or utilizes a particular landing system for performing landings.
-
E.
carriesLander
Indicates that one entity transports or holds a lander as its payload or cargo.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f877c988190928b6321c1f3f8f2 |
completed | May 2, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:34 p.m.