Triple
T2302707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenix Park |
E51767
|
entity |
| Predicate | hasWildlifePopulation |
P30476
|
FINISHED |
| Object | fallow deer herd |
—
|
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: fallow deer herd | Statement: [Phoenix Park, hasWildlifePopulation, fallow deer herd]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWildlifePopulation Context triple: [Phoenix Park, hasWildlifePopulation, fallow deer herd]
-
A.
hasWildPopulationOf
chosen
Indicates that a location or area contains a naturally occurring, non-captive population of the specified species.
-
B.
hasNearbyWildlife
Indicates that there is wildlife located close to or in the immediate vicinity of the referenced entity.
-
C.
hasEndemicSpecies
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
-
D.
hasBiodiversityFeature
Indicates that an entity possesses or is associated with a specific biodiversity-related characteristic, attribute, or element.
-
E.
hasExtinctSpecies
Indicates that at least one species associated with the subject entity is no longer extant (i.e., has gone extinct).
- 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_69a88b0a9f248190bcff941463d8f65a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcbabf01081908db3b42bc7c60444 |
completed | March 7, 2026, 6:54 a.m. |
| PD | Predicate disambiguation | batch_69abc58ad33c8190b8d68af41b6f5e07 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.