Triple
T19386099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Eye spring |
E484937
|
entity |
| Predicate | estimatedDepth |
P16570
|
FINISHED |
| Object | more than 50 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: more than 50 metres | Statement: [Blue Eye spring, estimatedDepth, more than 50 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedDepth Context triple: [Blue Eye spring, estimatedDepth, more than 50 metres]
-
A.
searchDepth
Indicates the extent or level to which a search process explores through layers, steps, or hierarchy within a structure or space.
-
B.
designedTargetDepthInKilometers
Indicates the intended or planned depth, measured in kilometers, that something is designed to reach or operate at.
-
C.
hasAverageDepth
Indicates that an entity possesses a specified mean depth value, typically measured over its entire extent or area.
-
D.
depthMetresApprox
chosen
Indicates an approximate measurement of how deep something is in metres, rather than an exact value.
-
E.
testDepth
Indicates that an entity is evaluated or measured based on how deep or thorough it is, often in terms of levels, layers, or extent below a surface or baseline.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b40d1148190b4fcd9ad56aa6910 |
completed | April 20, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.