Triple
T31024906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JP-4 |
E790542
|
entity |
| Predicate | flashPointApprox |
P87493
|
FINISHED |
| Object | around −23 °C |
—
|
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 −23 °C | Statement: [JP-4, flashPointApprox, around −23 °C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flashPointApprox Context triple: [JP-4, flashPointApprox, around −23 °C]
-
A.
hasTypicalFlashPoint
chosen
Indicates that one entity characteristically reaches its flash point (ignition temperature) at the temperature value specified by the other entity.
-
B.
consideredFlashpointBy
Indicates that something is regarded as a source of tension, conflict, or potential escalation by a particular party or group.
-
C.
flashType
Indicates the type or mode of flash used or associated with an event, object, or action.
-
D.
hasHigherFlashPointThan
Indicates that the flash point (the lowest temperature at which vapors ignite) of one substance is greater than that of another substance.
-
E.
beamApprox
Indicates that one entity is approximately equal to or closely resembles another in value, form, or behavior.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:58 p.m.