Triple
T3438028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Askival |
E72500
|
entity |
| Predicate | hasWildlifeContext |
P22447
|
FINISHED |
| Object | important habitat for red deer |
—
|
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: important habitat for red deer | Statement: [Askival, hasWildlifeContext, important habitat for red deer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWildlifeContext Context triple: [Askival, hasWildlifeContext, important habitat for red deer]
-
A.
hasNearbyWildlife
Indicates that there is wildlife located close to or in the immediate vicinity of the referenced entity.
-
B.
associatedWithWildlifeArea
Indicates that an entity has a connection, involvement, or linkage with a designated wildlife area.
-
C.
hasNearbyWildernessArea
Indicates that a wilderness area is located within a close geographic proximity to the referenced place or entity.
-
D.
hasBiodiversityFeature
chosen
Indicates that an entity possesses or is associated with a specific biodiversity-related characteristic, attribute, or element.
-
E.
usesLiveAnimals
Indicates that one entity employs or incorporates live animals in performing an action, service, process, or activity involving another entity.
- 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9f575cc8190866929b1e8930143 |
completed | March 8, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69adae00ad588190bef24373b58a2e1a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.