Triple
T6889663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carboniferous Limestone |
E159012
|
entity |
| Predicate | porosityType |
P12321
|
FINISHED |
| Object | fracture porosity |
—
|
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: fracture porosity | Statement: [Carboniferous Limestone, porosityType, fracture porosity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: porosityType Context triple: [Carboniferous Limestone, porosityType, fracture porosity]
-
A.
porosity
chosen
Indicates the degree to which a material or structure contains voids or pores relative to its total volume.
-
B.
permeability
Indicates how easily a substance, material, or barrier allows another substance (such as a fluid, gas, or signal) to pass through it.
-
C.
surfaceType
Indicates the kind or classification of surface associated with an entity or interaction.
-
D.
typeOfSedimentation
Indicates the specific kind or process of sediment deposition or settling that characterizes how sediment accumulates in a given context.
-
E.
nozzleType
Indicates the specific kind or category of nozzle associated with or used by an 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d9117c84819093dad7b765337b63 |
completed | March 27, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b53e9881909ec298daa9f1913b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:23 p.m.