Triple
T15302742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odda |
E365827
|
entity |
| Predicate | fjordType |
P56784
|
FINISHED |
| Object | branch of Hardangerfjorden |
—
|
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: branch of Hardangerfjorden | Statement: [Odda, fjordType, branch of Hardangerfjorden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fjordType Context triple: [Odda, fjordType, branch of Hardangerfjorden]
-
A.
hasFjord
chosen
Indicates that an entity possesses, contains, or is characterized by a fjord as part of its geography or features.
-
B.
hasNearbyFjord
Indicates that one entity is located close to or in the vicinity of a fjord associated with another entity.
-
C.
seafloorType
Indicates the classification of the ocean bottom surface based on its physical or geological characteristics.
-
D.
glacierType
Indicates the specific classification or category of a glacier based on its form, dynamics, or setting.
-
E.
basinType
Indicates the specific kind or classification of a basin associated with an entity (e.g., by form, function, or hydrological role).
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ccd575c8190aa43262d3b73ef3c |
completed | April 16, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:15 a.m.