Triple
T37566103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 16 |
E933959
|
entity |
| Predicate | returnVehicleUsed |
P12443
|
FINISHED |
| Object | Soyuz TMA-11 |
—
|
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-11 | Statement: [Expedition 16, returnVehicleUsed, Soyuz TMA-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnVehicleUsed Context triple: [Expedition 16, returnVehicleUsed, Soyuz TMA-11]
-
A.
returnedToUse
Indicates that something previously inactive, unavailable, or discontinued has been put back into active use or operation.
-
B.
vehicleUsed
chosen
Indicates that a particular vehicle is utilized or employed in performing an action, event, or activity.
-
C.
usedAsVehicleFor
Indicates that one entity functions as a means of transportation or conveyance for another entity.
-
D.
usedAsReleaseVehicleFor
Indicates that one entity is employed as the means or mechanism to launch, distribute, or deliver another entity.
-
E.
hasVehicularUse
Indicates that something is used for, intended for, or associated with operation by vehicles or vehicular traffic.
- 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_69f76ecb4acc8190b53f96d0b013e415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 3, 2026, 4:17 p.m.