Triple
T21486068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian fjords |
E530118
|
entity |
| Predicate | hasMaxDepthOver |
P1177
|
FINISHED |
| Object | 1000 metres in some fjords |
—
|
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: 1000 metres in some fjords | Statement: [Norwegian fjords, hasMaxDepthOver, 1000 metres in some fjords]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaxDepthOver Context triple: [Norwegian fjords, hasMaxDepthOver, 1000 metres in some fjords]
-
A.
hasMaximumDepth
chosen
Indicates that an entity possesses a greatest or limiting depth value beyond which it does not extend.
-
B.
hasDepth
Indicates that an entity possesses a measurable extent or distance from its surface inward or from top to bottom.
-
C.
hasUnknownMaximumDepth
Indicates that the maximum depth associated with an entity or process is not known or cannot be determined.
-
D.
reachedDepth
Indicates that an entity has arrived at or attained a specified depth level in some medium or context.
-
E.
maximumDepth
Indicates the greatest extent or deepest level reached by something within a given context or structure.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea370adc8190b79fe26e2eba1dca |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:22 p.m.