Triple
T10787798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LM |
E254492
|
entity |
| Predicate | environmentOfOperation |
P9320
|
FINISHED |
| Object | vacuum of space |
—
|
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: vacuum of space | Statement: [LM, environmentOfOperation, vacuum of space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: environmentOfOperation Context triple: [LM, environmentOfOperation, vacuum of space]
-
A.
environmentType
Indicates the kind or category of environment associated with an entity or situation.
-
B.
appliesToOperationalEnvironment
Indicates that something (such as a rule, requirement, or condition) is relevant to, valid in, or specifically intended for a particular operational environment.
-
C.
primaryOperatingEnvironment
chosen
Indicates the main environment, platform, or context in which an entity is primarily designed to operate or function.
-
D.
operatingCondition
Indicates the specific state, requirements, or circumstances under which an entity functions or is intended to be used.
-
E.
operatesInEcosystem
Indicates that an entity functions, behaves, or carries out its activities within a particular ecosystem or environmental context.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d65fcc8190ab5573a861409c56 |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.