Triple
T33124612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zurich Zoo |
E847687
|
entity |
| Predicate | zooAssociationAccreditation |
P19449
|
FINISHED |
| Object | EAZA accredited |
—
|
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: EAZA accredited | Statement: [Zurich Zoo, zooAssociationAccreditation, EAZA accredited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zooAssociationAccreditation Context triple: [Zurich Zoo, zooAssociationAccreditation, EAZA accredited]
-
A.
zooAccreditation
chosen
Indicates that an entity (such as a zoo or aquarium) holds a formal accreditation or certification from a recognized accrediting organization.
-
B.
zooSignificance
Indicates the degree to which something is important, relevant, or meaningful in the context of a zoo.
-
C.
zooAlternativeName
Indicates that a zoo is known by an alternative or additional name.
-
D.
zooSpecialization
Indicates that one entity is a zoo whose primary focus or expertise is specialized in the type, category, or group represented by the other entity.
-
E.
isMajorZooIn
Indicates that a zoo is a primary or significant zoological institution located within a specified geographic area or 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d71dc75c8190886ea8c2ab87b323 |
completed | May 3, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.