Triple
T15235205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greensand |
E364109
|
entity |
| Predicate | hasPermeability |
P48525
|
FINISHED |
| Object | moderate permeability |
—
|
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: moderate permeability | Statement: [Greensand, hasPermeability, moderate permeability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPermeability Context triple: [Greensand, hasPermeability, moderate permeability]
-
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.
hasPermit
Indicates that an entity possesses an official authorization or license granting it permission to perform a specific activity or hold a certain status.
-
C.
isPassedThroughBy
Indicates that something serves as a medium, route, or channel through which another thing moves, flows, or is transmitted.
-
D.
hasBorderThrough
Indicates that a border between two regions or entities passes through or along a specified intermediate area, feature, or object.
-
E.
hasViewThrough
Indicates that one entity can be seen or visually perceived through another entity acting as an intermediate medium or opening.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007d91e4881908ea52d11a3d4480a |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:12 a.m.