Triple
T7523897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-90 |
E177842
|
entity |
| Predicate | usedLaboratory |
P74015
|
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: [STS-90, usedLaboratory, Spacelab module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedLaboratory Context triple: [STS-90, usedLaboratory, Spacelab module]
-
A.
aboardLaboratory
Indicates that an entity is physically present on or within a laboratory facility, such as being on board a lab-equipped platform, vehicle, or structure.
-
B.
laboratoryModule
Indicates a relationship where an entity is a laboratory module or functions as a lab-specific component or unit within a larger system or structure.
-
C.
laboratoryMedium
Indicates that one entity serves as the culture or growth medium used in a laboratory context for another entity.
-
D.
hasLaboratorySystem
chosen
Indicates that one entity possesses, uses, or is associated with a particular laboratory system.
-
E.
usedInWork
Indicates that something (such as a concept, method, material, or component) is employed or applied within a particular work, project, or creation.
- 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_69c69f29bf3081909a146aec7755f185 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f7c61b508190b582f54ecbb387e3 |
completed | March 27, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:46 p.m.