Triple
T26726872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MMU backpack |
E673857
|
entity |
| Predicate | environmentOfUse |
P13408
|
FINISHED |
| Object | low Earth orbit |
—
|
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: low Earth orbit | Statement: [MMU backpack, environmentOfUse, low Earth orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: environmentOfUse Context triple: [MMU backpack, environmentOfUse, low Earth orbit]
-
A.
environmentType
Indicates the kind or category of environment associated with an entity or situation.
-
B.
usedInEnvironment
chosen
Indicates that something is utilized or operates within a particular environment or context.
-
C.
environmentSubtype
Indicates that one environment is a more specific subtype or category within another, more general environment.
-
D.
environmentAnalogOf
Indicates that one environment serves as an analogue or counterpart to another, typically mirroring its conditions, structure, or behavior for comparison or simulation purposes.
-
E.
environmentIncludes
Indicates that a given environment contains, encompasses, or has within it the specified entity or component.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 3:43 a.m.