Triple
T28379916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPI Adventure |
E718861
|
entity |
| Predicate | deckSpace |
P77125
|
FINISHED |
| Object | large open deck for turbine components |
—
|
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: large open deck for turbine components | Statement: [MPI Adventure, deckSpace, large open deck for turbine components]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deckSpace Context triple: [MPI Adventure, deckSpace, large open deck for turbine components]
-
A.
hasCrewQuarters
Indicates that one entity provides or contains designated living or sleeping quarters for the crew associated with it.
-
B.
spaceType
chosen
Indicates the category or kind of physical or conceptual space associated with an entity.
-
C.
IOSpace
Indicates a relationship where an entity occupies, defines, or is associated with a specific input/output address space or memory-mapped I/O region.
-
D.
mainSpaceStation
Indicates that one entity serves as the primary or central space station associated with another entity.
-
E.
spaceStationExpedition
Indicates a mission or expedition undertaken to travel to, work on, or return from a space station.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64cb538448190be1c85c33d6bdd62 |
completed | May 2, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:05 a.m.