Triple
T26906459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planckendael Zoo |
E677267
|
entity |
| Predicate | sharesManagingSocietyWith |
P45995
|
FINISHED |
| Object | Antwerp Zoo |
—
|
NE NERFINISHED |
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: Antwerp Zoo | Statement: [Planckendael Zoo, sharesManagingSocietyWith, Antwerp Zoo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesManagingSocietyWith Context triple: [Planckendael Zoo, sharesManagingSocietyWith, Antwerp Zoo]
-
A.
sharesOwnershipWith
Indicates that two or more entities jointly hold ownership rights or stakes in the same asset, resource, or organization.
-
B.
managingOrganisation
Indicates that one organisation has responsibility for directing, overseeing, or administering another entity or activity.
-
C.
sharesAdministrationWith
chosen
Indicates that two entities are jointly managed, governed, or overseen by the same administrative body or authority.
-
D.
sharesFounderWith
Indicates that two entities have at least one founder in common.
-
E.
sharesHarborWith
Indicates that two entities use or are associated with the same harbor.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 27, 2026, 5:59 a.m.