Triple
T7727796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D-2 |
E175176
|
entity |
| Predicate | spacelabModule |
P78824
|
FINISHED |
| Object | Spacelab module |
—
|
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: Spacelab module | Statement: [D-2, spacelabModule, Spacelab module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spacelabModule Context triple: [D-2, spacelabModule, Spacelab module]
-
A.
spacelabSeries
chosen
Indicates that one entity is part of, or belongs to, a particular series of Spacelab missions or modules.
-
B.
spaceStationModuleUsed
Indicates that a particular space station module is utilized or occupied for a specific purpose or activity.
-
C.
spaceCenter
Indicates that one entity serves as a primary facility or hub for space-related operations, missions, or administration for another entity.
-
D.
spacecraftComponents
Indicates that one entity is a spacecraft and the other is a component or part that belongs to or is used in that spacecraft.
-
E.
spaceStationConfiguration
Indicates the specific structural and functional arrangement of modules, systems, and components that define how a space station is organized and operates.
- 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_69c6995e912c81909a49a2657103f786 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c708bcba5c81908f00aa9e80e17f1b |
completed | March 27, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69c708ae9da081908d36d48979b9600f |
completed | March 27, 2026, 10:46 p.m. |
Created at: March 27, 2026, 4:06 p.m.