Triple
T6885985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sassen–Bünsow Land National Park |
E158918
|
entity |
| Predicate | hasTypicalFauna |
P22447
|
FINISHED |
| Object | polar bear |
—
|
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: polar bear | Statement: [Sassen–Bünsow Land National Park, hasTypicalFauna, polar bear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalFauna Context triple: [Sassen–Bünsow Land National Park, hasTypicalFauna, polar bear]
-
A.
fauna
Indicates that an entity is an animal or part of the animal life associated with a particular place or context.
-
B.
hasBiodiversityFeature
chosen
Indicates that an entity possesses or is associated with a specific biodiversity-related characteristic, attribute, or element.
-
C.
hasNativeSpecies
Indicates that a particular species naturally occurs and evolved in a specified geographic area or habitat, rather than being introduced from elsewhere.
-
D.
faunaCharacteristic
Indicates that an entity has a specific trait, feature, or quality related to animals or animal life.
-
E.
hasEndemicSpecies
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
- 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_69c688342f6c8190ad7eea6ba262db99 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d90bc32c8190baf5bf785146f3e8 |
completed | March 27, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b53e9881909ec298daa9f1913b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:23 p.m.