Triple
T3626192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nærøyfjord |
E76844
|
entity |
| Predicate | widthAtNarrowestPoint |
P619
|
FINISHED |
| Object | approximately 250 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: approximately 250 metres | Statement: [Nærøyfjord, widthAtNarrowestPoint, approximately 250 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: widthAtNarrowestPoint Context triple: [Nærøyfjord, widthAtNarrowestPoint, approximately 250 metres]
-
A.
isNarrowestPartOf
Indicates that one entity constitutes the slimmest or most constricted section within the extent or structure of another entity.
-
B.
width
chosen
Indicates the measurement of how wide an entity is, typically the extent of its horizontal dimension from side to side.
-
C.
isNarrow
Indicates that something has a small width or limited breadth relative to a reference or context.
-
D.
minimumWidth
Indicates that there is a specified smallest allowable or required width for something in the relationship.
-
E.
lowestPoint
Indicates that one entity is the point with the minimum vertical position or value relative to another entity or within a specified context.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2dc011c8190a6596f4b483fb078 |
completed | March 8, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69adb8410a5881909c94818d7060b2b0 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.