Triple
T31654285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Djauro |
E807817
|
entity |
| Predicate | nativeTitleClaimsIn |
P48929
|
FINISHED |
| Object | Broome region |
—
|
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: Broome region | Statement: [Djauro, nativeTitleClaimsIn, Broome region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeTitleClaimsIn Context triple: [Djauro, nativeTitleClaimsIn, Broome region]
-
A.
nativeTitleOutcome
Indicates the result or status achieved in relation to a native or original title (such as a formal designation, rank, or work title) following some process or event.
-
B.
nativeTitleState
Indicates the state or condition of an entity’s original or native title (e.g., whether it is present, valid, active, or in a particular status).
-
C.
nativeTitleDeterminationAreaIncludes
Indicates that a specified native title determination area geographically encompasses or includes another area.
-
D.
nativeTitleInvolvement
Indicates that an entity is involved with or associated with a title expressed in its original (native) language.
-
E.
hasNativeTitleClaimsOver
chosen
Indicates that an entity holds recognized native or indigenous title rights or claims over a specified area or resource.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 10:54 p.m.