Triple
T31691302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jukun |
E808799
|
entity |
| Predicate | hasNativeTitleInterestNear |
P196466
|
FINISHED |
| Object | Broome |
—
|
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 | Statement: [Jukun, hasNativeTitleInterestNear, Broome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNativeTitleInterestNear Context triple: [Jukun, hasNativeTitleInterestNear, Broome]
-
A.
hasNativeTitleClaimsOver
Indicates that an entity holds recognized native or indigenous title rights or claims over a specified area or resource.
-
B.
hasNativeTitleDetermination
Indicates that an entity has an associated legal or official determination regarding native title rights or interests.
-
C.
hasNativeTitleAgreementsIn
Indicates that an entity is subject to or involved in native title agreements within a specified jurisdiction or geographic area.
-
D.
nativeTitleInvolvement
Indicates that an entity is involved with or associated with a title expressed in its original (native) language.
-
E.
nativeTitleDeterminationAreaIncludes
Indicates that a specified native title determination area geographically encompasses or includes another 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
| PDg | Predicate description generation | batch_69fe38bc3e9c8190838430b22b82503f |
completed | May 8, 2026, 7:25 p.m. |
Created at: April 30, 2026, 11:08 p.m.