Triple
T35221263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munga-Thirri National Park |
E1016960
|
entity |
| Predicate | hasWildlifeCharacteristic |
P182627
|
FINISHED |
| Object | arid-adapted species |
—
|
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: arid-adapted species | Statement: [Munga-Thirri National Park, hasWildlifeCharacteristic, arid-adapted species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWildlifeCharacteristic Context triple: [Munga-Thirri National Park, hasWildlifeCharacteristic, arid-adapted species]
-
A.
hasWildlifeHabitats
Indicates that an entity contains or supports natural environments where wildlife species live, feed, or reproduce.
-
B.
hasWildlifeSite
Indicates that a location or entity possesses, contains, or is designated as a wildlife site.
-
C.
hasWildlifeStatus
Indicates the conservation or protection status assigned to wildlife associated with an entity.
-
D.
hasWildlifeActivity
Indicates that wildlife is present in the area and engaging in observable behaviors or movements.
-
E.
hasWildlifeRegion
Indicates that an entity is associated with or located within a designated wildlife region or habitat area.
- F. None of above. chosen
Provenance (4 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_69f76de072908190ab65038a8a7b6a79 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904a770481908ef3f788e51e8dba |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:02 p.m.