Triple
T14681850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LZ 129 Hindenburg |
E344805
|
entity |
| Predicate | gasVolume |
P22265
|
FINISHED |
| Object | 200000 m³ |
—
|
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: 200000 m³ | Statement: [LZ 129 Hindenburg, gasVolume, 200000 m³]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gasVolume Context triple: [LZ 129 Hindenburg, gasVolume, 200000 m³]
-
A.
volumeOf
Indicates the quantitative three-dimensional space occupied by an entity or contained within an object.
-
B.
gasContent
chosen
Indicates that one entity has, contains, or is characterized by a certain amount or type of gas.
-
C.
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.
-
D.
pressurizedVolume
Indicates that a specified volume is maintained at a pressure different from ambient (typically higher), often as part of a controlled or sealed system.
-
E.
typeOfGasUsed
Indicates the specific kind of gas that is utilized in relation to an entity or process.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb56a51ec8190941684fd562a7182 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.