Triple
T32503408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strigopoidea |
E830721
|
entity |
| Predicate | containsAlpineTaxon |
P45064
|
FINISHED |
| Object | Nestor notabilis (kea) |
—
|
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: Nestor notabilis (kea) | Statement: [Strigopoidea, containsAlpineTaxon, Nestor notabilis (kea)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsAlpineTaxon Context triple: [Strigopoidea, containsAlpineTaxon, Nestor notabilis (kea)]
-
A.
hasAlpineFlora
Indicates that an entity possesses or is characterized by plant life typical of high-altitude alpine environments.
-
B.
hasAlpineTundra
Indicates that something possesses or is characterized by an alpine tundra environment or habitat.
-
C.
includesTaxaWith
chosen
Indicates that an entity contains or encompasses one or more specified taxa within its scope or membership.
-
D.
includesExampleTaxon
Indicates that a taxonomic group or concept contains a specific taxon used as an illustrative or representative example.
-
E.
includesFamiliarTaxa
Indicates that the referenced group or set contains taxa that are commonly known or recognizable.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ffdd05d1908190957deb11392f4595 |
completed | May 10, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69ffdc0d33c881908b3483bee8a96540 |
completed | May 10, 2026, 1:14 a.m. |
Created at: May 1, 2026, 12:59 a.m.