Triple
T24584787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hinlopen Strait |
E608354
|
entity |
| Predicate | hasCountryJurisdiction |
P7728
|
FINISHED |
| Object | Kingdom of Norway |
—
|
NE NERFINISHED |
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: Kingdom of Norway | Statement: [Hinlopen Strait, hasCountryJurisdiction, Kingdom of Norway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountryJurisdiction Context triple: [Hinlopen Strait, hasCountryJurisdiction, Kingdom of Norway]
-
A.
countryJurisdiction
Indicates that one country has legal authority, control, or governing power over a specified territory, entity, or matter.
-
B.
countryOfJurisdiction
chosen
Indicates the country whose legal authority or jurisdiction governs or applies to a given entity, action, or arrangement.
-
C.
flagJurisdiction
Indicates that a flag is associated with, governed by, or represents a particular jurisdiction or legal authority.
-
D.
hasPoliticalJurisdictionType
Indicates the type or category of political jurisdiction that applies to or governs an entity.
-
E.
existsInJurisdiction
Indicates that an entity is located within, falls under, or is subject to the authority of a particular legal or administrative jurisdiction.
- 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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a98600888190aa631d2c237af60a |
completed | April 30, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.