Triple
T23008987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz TMA-10 |
E572854
|
entity |
| Predicate | roleInISSProgram |
P110710
|
FINISHED |
| Object | crew rotation |
—
|
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: crew rotation | Statement: [Soyuz TMA-10, roleInISSProgram, crew rotation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInISSProgram Context triple: [Soyuz TMA-10, roleInISSProgram, crew rotation]
-
A.
roleInSpaceX
Indicates that one entity holds or has held a specific role, position, or function within the organization SpaceX.
-
B.
roleInSpaceShipOneProgram
Indicates that an entity has a specific role or involvement in the SpaceShipOne program.
-
C.
spaceStationRole
chosen
Indicates the functional role or duty an entity has in relation to a space station.
-
D.
roleInRelationToNASA
Indicates that one entity holds a specific role, position, or functional relationship with respect to NASA.
-
E.
attachedToSpaceStation
Indicates that an object is physically connected or secured to a space station.
- 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1835919b08190ba78e182b87358d4 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.