Triple
T12617424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Svalbard fisheries protection zone |
E301289
|
entity |
| Predicate | mainResourceManaged |
P86412
|
FINISHED |
| Object | cod fisheries |
—
|
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: cod fisheries | Statement: [Svalbard fisheries protection zone, mainResourceManaged, cod fisheries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainResourceManaged Context triple: [Svalbard fisheries protection zone, mainResourceManaged, cod fisheries]
-
A.
mainAssetManaged
Indicates that one entity is responsible for managing another entity that serves as the primary or main asset.
-
B.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
C.
isManaged
Indicates that one entity exercises supervisory or administrative control over another entity.
-
D.
managedAs
Indicates that one entity is administered, controlled, or handled in the same way or under the same policies, procedures, or classification as another entity.
-
E.
managesResourceType
chosen
Indicates that an entity is responsible for overseeing, controlling, or administering a particular type or category of resource.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:13 p.m.