Triple
T4389283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RP-1 |
E99321
|
entity |
| Predicate | handlingProperty |
P56319
|
FINISHED |
| Object | easierToStoreThanCryogenicHydrogen |
—
|
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: easierToStoreThanCryogenicHydrogen | Statement: [RP-1, handlingProperty, easierToStoreThanCryogenicHydrogen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlingProperty Context triple: [RP-1, handlingProperty, easierToStoreThanCryogenicHydrogen]
-
A.
handlingRequirement
Indicates the specific conditions, precautions, or procedures that must be followed when handling an item, substance, or entity.
-
B.
handles
Indicates that one entity is responsible for dealing with, managing, or taking care of another entity or task.
-
C.
handledLanguage
Indicates that an entity has processed, used, or otherwise dealt with a particular language in some context.
-
D.
messageHandling
Indicates how messages are received, processed, and responded to within a communication or messaging system.
-
E.
canHandle
Indicates that an entity has the ability or capacity to manage, process, or deal with another entity or situation.
- F. None of above. chosen
Provenance (4 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35281900c8190882e9ccfa44ab86f |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3501834448190bedf775a80da4778 |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:19 p.m.