Triple
T26121967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loddon Mallee region |
E658993
|
entity |
| Predicate | containsBioregion |
P123911
|
FINISHED |
| Object | Mallee |
—
|
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: Mallee | Statement: [Loddon Mallee region, containsBioregion, Mallee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsBioregion Context triple: [Loddon Mallee region, containsBioregion, Mallee]
-
A.
includesZoogeographicSubregion
chosen
Indicates that a broader zoogeographic region contains or encompasses a specific zoogeographic subregion within its boundaries.
-
B.
hasBiosphere
Indicates that an entity possesses or supports a biosphere, i.e., a region where living organisms and ecological processes exist.
-
C.
isInBiosphere
Indicates that an entity exists within, or is a component of, the Earth's biosphere (the global sum of all ecosystems and living environments).
-
D.
belongsToBiogeographicRealm
Indicates that an entity (such as a species, habitat, or location) is associated with or falls within a particular biogeographic realm.
-
E.
hasMajorEcoregion
Indicates that an entity is primarily located within, or chiefly associated with, a particular major ecological region.
- 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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 26, 2026, 8:09 p.m.