Triple
T20284362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Müritz |
E509836
|
entity |
| Predicate | hasAverageDepthApprox |
P1176
|
FINISHED |
| Object | about 6 m |
—
|
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: about 6 m | Statement: [Müritz, hasAverageDepthApprox, about 6 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAverageDepthApprox Context triple: [Müritz, hasAverageDepthApprox, about 6 m]
-
A.
hasAverageDepth
chosen
Indicates that an entity possesses a specified mean depth value, typically measured over its entire extent or area.
-
B.
hasApproximateDepth
Indicates that an entity is associated with a depth value that is not exact but estimated or approximate.
-
C.
hasDepth
Indicates that an entity possesses a measurable extent or distance from its surface inward or from top to bottom.
-
D.
hasChannelDepth
Indicates that one entity specifies or records the depth measurement of a channel associated with another entity.
-
E.
hasAverageSurfaceSpeed
Indicates the typical or mean speed at which something moves across a surface over a given period or distance.
- 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_69e0b4c652388190b782cad965e5a098 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67691516c81909f32b176edb6214c |
completed | April 20, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:05 a.m.