Triple
T5571778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sør-Spitsbergen National Park |
E146217
|
entity |
| Predicate | hasColonyType |
P30272
|
FINISHED |
| Object | seabird colonies |
—
|
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: seabird colonies | Statement: [Sør-Spitsbergen National Park, hasColonyType, seabird colonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColonyType Context triple: [Sør-Spitsbergen National Park, hasColonyType, seabird colonies]
-
A.
colonyType
chosen
Indicates the specific classification or kind of colony associated with an entity (e.g., its organizational or structural type).
-
B.
colonyOf
Indicates that one entity is a colony belonging to, founded by, or politically dependent on another entity.
-
C.
operatedInColony
Indicates that an entity conducted operations or activities within a specific colony.
-
D.
colonyStatus
Indicates the political or administrative condition of a territory in relation to a colonizing power, such as whether it is a colony, former colony, or non-colonial.
-
E.
endedInMainColony
Indicates that an event, process, or entity concluded within the primary or central colony rather than elsewhere.
- 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_69c008ffed108190a084602227af6157 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020518f348190879ac67dab307134 |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b147cc081909237f3f2967d4cb8 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:37 p.m.