Triple
T17245740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Large Space Simulator |
E418619
|
entity |
| Predicate | canReachPressure |
P56372
|
FINISHED |
| Object | around 10^-6 millibar |
—
|
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: around 10^-6 millibar | Statement: [Large Space Simulator, canReachPressure, around 10^-6 millibar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canReachPressure Context triple: [Large Space Simulator, canReachPressure, around 10^-6 millibar]
-
A.
hasHumanPressure
Indicates that one entity exerts or experiences human-induced influence, stress, or impact in relation to another entity or environment.
-
B.
pressureCapability
chosen
Indicates the maximum pressure an entity can safely exert, withstand, or operate under within a given context.
-
C.
hasPressureSphere
Indicates a relationship where an entity possesses or is associated with a defined region or volume characterized by a specific pressure condition.
-
D.
hasApproximatePressure
Indicates that one entity has a pressure value that is approximately equal to the pressure value associated with another entity or reference.
-
E.
hasGroundPressure
Indicates that an entity exerts a specific amount of pressure on the ground or surface it is in contact with.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e23b8948190870d0e6b4e55b4e3 |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.