Triple
T31793460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 18 |
E811528
|
entity |
| Predicate | spacecraftVisited |
P177589
|
FINISHED |
| Object | Space Shuttle Endeavour STS-126 |
—
|
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: Space Shuttle Endeavour STS-126 | Statement: [Expedition 18, spacecraftVisited, Space Shuttle Endeavour STS-126]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spacecraftVisited Context triple: [Expedition 18, spacecraftVisited, Space Shuttle Endeavour STS-126]
-
A.
cargoSpacecraftVisited
Indicates that a cargo spacecraft has made a visit to a particular location or object.
-
B.
exploredBySpacecraft
Indicates that a celestial object or region has been visited, observed, or studied directly by a spacecraft.
-
C.
spacecraftDestination
Indicates that a spacecraft is intended to travel to, arrive at, or be directed toward a particular destination.
-
D.
spaceflightDestination
Indicates the target location or body in space that a spaceflight is intended to reach.
-
E.
orbitsBeyond
Indicates that one celestial body orbits at a greater average distance from a central object than another specified body.
- F. None of above. chosen
Provenance (4 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: April 30, 2026, 11:39 p.m.