Triple
T38152877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRS-16 |
E952801
|
entity |
| Predicate | targetSpaceStation |
P52854
|
FINISHED |
| Object | International Space Station |
—
|
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: International Space Station | Statement: [CRS-16, targetSpaceStation, International Space Station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetSpaceStation Context triple: [CRS-16, targetSpaceStation, International Space Station]
-
A.
spaceStationExpedition
Indicates a mission or expedition undertaken to travel to, work on, or return from a space station.
-
B.
mainSpaceStation
Indicates that one entity serves as the primary or central space station associated with another entity.
-
C.
spaceStationName
Indicates that an entity has the specified name of a space station.
-
D.
spaceStationServed
chosen
Indicates that a particular space station is or was serviced, supplied, or supported by a specific mission, vehicle, or service entity.
-
E.
spaceStationType
Indicates the specific functional or structural category to which a space station belongs (e.g., research, military, commercial).
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff56ef0a5c8190ae729d66a8cf7fc4 |
completed | May 9, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ff539859c481909ec56310da418688 |
completed | May 9, 2026, 3:32 p.m. |
Created at: May 3, 2026, 4:21 p.m.