Triple
T1199692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australasian realm |
E25750
|
entity |
| Predicate | hasEndemicTaxa |
P954
|
FINISHED |
| Object | many marsupial genera |
—
|
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: many marsupial genera | Statement: [Australasian realm, hasEndemicTaxa, many marsupial genera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndemicTaxa Context triple: [Australasian realm, hasEndemicTaxa, many marsupial genera]
-
A.
hasEndemicSpecies
chosen
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
-
B.
hasEndemismLevel
Indicates the degree to which something is restricted or native to a particular geographic area or region.
-
C.
areEndangeredIn
Indicates that the entities are classified as endangered within a specified geographic area or jurisdiction.
-
D.
hasSolitarySpecies
Indicates that an entity includes or is associated with species that live or behave predominantly alone rather than in groups.
-
E.
hasLivingSpecies
Indicates that an entity currently contains, supports, or is associated with one or more species that are alive or extant.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd9d56748190a12fe4a30346f1d8 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5ed2b88190aab992913957e1cf |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.