Triple
T2959180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skansen |
E80003
|
entity |
| Predicate | zooSpecialization |
P45213
|
FINISHED |
| Object | Nordic animals |
—
|
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: Nordic animals | Statement: [Skansen, zooSpecialization, Nordic animals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zooSpecialization Context triple: [Skansen, zooSpecialization, Nordic animals]
-
A.
zooSection
Indicates that one entity is a specific section or area within a zoo where the other entity is located, organized, or assigned.
-
B.
zooAccreditation
Indicates that an entity (such as a zoo or aquarium) holds a formal accreditation or certification from a recognized accrediting organization.
-
C.
zooSectionType
Indicates the specific type or category of section within a zoo that an area or enclosure belongs to.
-
D.
hasZoo
Indicates that one entity possesses, operates, or is associated with a zoo.
-
E.
frozenZooDescription
Indicates that an entity provides a description or summary of a frozen zoo, typically detailing its preserved biological specimens or related information.
- F. None of above. chosen
Provenance (4 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad992c4c7c819084b5bef299255181 |
completed | March 8, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69ad960c5c8881909d679912bd7d78f3 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad98379fac8190a4dfe530787703c9 |
completed | March 8, 2026, 3:39 p.m. |
Created at: March 8, 2026, 2:57 p.m.