Triple
T9655720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pumice Desert |
E233444
|
entity |
| Predicate | substratePermeability |
P48525
|
FINISHED |
| Object | very high |
—
|
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: very high | Statement: [Pumice Desert, substratePermeability, very high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: substratePermeability Context triple: [Pumice Desert, substratePermeability, very high]
-
A.
permeability
chosen
Indicates how easily a substance, material, or barrier allows another substance (such as a fluid, gas, or signal) to pass through it.
-
B.
hasSubstrateInfluenceOn
Indicates that one substrate affects, modifies, or determines the behavior, activity, or properties of another entity or process.
-
C.
porosity
Indicates the degree to which a material or structure contains voids or pores relative to its total volume.
-
D.
isSubstrateOf
Indicates that one entity serves as the material or reactant upon which another entity (typically an enzyme or process) acts in a chemical or biochemical reaction.
-
E.
possibleSubstrateIn
Indicates that one entity can potentially serve as a substrate or reactant within a process, reaction, or system represented by the other entity.
- 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_69ca848c1ba88190b84b410cd14627fc |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9bdbdd948190a4545a5df0f7af77 |
completed | April 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:13 p.m.