Triple
T27549052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 8 |
E695440
|
entity |
| Predicate | crewTransportSpacecraft |
P45020
|
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, crewTransportSpacecraft, Soyuz TMA-3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewTransportSpacecraft Context triple: [Expedition 8, crewTransportSpacecraft, Soyuz TMA-3]
-
A.
carriesCrewOf
chosen
Indicates that one entity serves as the vehicle or vessel that transports the crew belonging to another entity.
-
B.
usedCargoSpacecraftType
Indicates that a particular type of cargo spacecraft was employed or utilized in a given mission or context.
-
C.
hasShuttlecraft
Indicates that an entity possesses, controls, or is equipped with one or more shuttlecraft.
-
D.
intendedCrewVehicle
Indicates that a particular vehicle is designated or planned to be used by a specific crew.
-
E.
designedCrewVehicle
Indicates that an agent or entity is responsible for designing a vehicle intended to carry a crew.
- 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.