Triple
T4438496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Einstein–Szilard refrigerator |
E95710
|
entity |
| Predicate | usesGasLift |
P35806
|
FINISHED |
| Object | ammonia vapor to circulate butane |
—
|
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: ammonia vapor to circulate butane | Statement: [Einstein–Szilard refrigerator, usesGasLift, ammonia vapor to circulate butane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGasLift Context triple: [Einstein–Szilard refrigerator, usesGasLift, ammonia vapor to circulate butane]
-
A.
hasLift
Indicates that one entity is equipped with, contains, or provides access to a lift (elevator).
-
B.
roleInGas
Indicates that an entity has a specific functional or contextual role within a gas-related process, system, or environment.
-
C.
typeOfGasUsed
chosen
Indicates the specific kind of gas that is utilized in relation to an entity or process.
-
D.
gasSystem
Indicates a relationship where an entity functions as, is part of, or is associated with a gas-based system used for distribution, control, or processing of gases.
-
E.
gasReleased
Indicates that a gas is emitted or discharged from a source into its surrounding environment.
- 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_69b3453ea2b48190a26f154b3b8fece5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3558c75948190875a5fb10eac0597 |
completed | March 13, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69b34f6078cc8190831b89f404198cc5 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:31 p.m.