Triple
T35606474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flow Country peatlands |
E1028907
|
entity |
| Predicate | averagePeatDepth |
P1176
|
FINISHED |
| Object | several metres |
—
|
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: several metres | Statement: [Flow Country peatlands, averagePeatDepth, several metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: averagePeatDepth Context triple: [Flow Country peatlands, averagePeatDepth, several metres]
-
A.
permafrostDepth
Indicates the measured or estimated thickness or vertical extent of perennially frozen ground (permafrost) at a given location.
-
B.
hasAverageWaterDepth
Indicates that an entity is associated with a specified mean or typical depth of water over a given area or period.
-
C.
hasAverageDepth
chosen
Indicates that an entity possesses a specified mean depth value, typically measured over its entire extent or area.
-
D.
surfaceRegolithDepth_m
Indicates the measured thickness of the loose surface regolith layer at a location, expressed in meters.
-
E.
riverbedDepth
Indicates the depth or vertical distance from the water surface to the bottom of a river at a given location or time.
- 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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:05 p.m.