Triple
T11192616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durack |
E264837
|
entity |
| Predicate | containsRegionType |
P97770
|
FINISHED |
| Object | outback |
—
|
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: outback | Statement: [Durack, containsRegionType, outback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsRegionType Context triple: [Durack, containsRegionType, outback]
-
A.
includedSpecialRegionType
Indicates that a special or designated region is included within another region or context, specifying the type of that included special region.
-
B.
containsDialectRegion
Indicates that one linguistic variety or dataset includes or covers a specific dialect region within its scope.
-
C.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
D.
hasRegionFunction
Indicates that a region is associated with a particular function, role, or operational purpose.
-
E.
isKeyRegionFor
Indicates that one region plays a central or strategically important role in relation to a specified process, function, or larger 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8be025481909d311b587418dfb2 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf4461c8190af84060f7db83211 |
completed | April 9, 2026, 8:01 a.m. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:29 p.m.