Triple
T8597345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chizarira National Park |
E203583
|
entity |
| Predicate | birdLife |
P45421
|
FINISHED |
| Object | raptors |
—
|
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: raptors | Statement: [Chizarira National Park, birdLife, raptors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birdLife Context triple: [Chizarira National Park, birdLife, raptors]
-
A.
birdDiversity
Indicates the variety and richness of different bird species present within a given area, community, or dataset.
-
B.
majorBirdGroups
Indicates that the subject entity represents a major taxonomic or evolutionary grouping within birds that includes the object entity as a member or component.
-
C.
supportsBirdlife
chosen
Indicates that one entity provides conditions or resources that help sustain or benefit bird life associated with another entity.
-
D.
migratoryBirdsFrom
Indicates a relationship where the subject is a location or region that serves as the origin from which migratory birds travel or disperse.
-
E.
recognizedAsImportantBirdArea
Indicates that a location has been officially designated as an Important Bird Area due to its significance for bird conservation.
- 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46cacbe88190b95beeedc9f480b0 |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
Created at: March 30, 2026, 6:24 p.m.