Triple
T37331688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gomeroi Native Title Applicant |
E926767
|
entity |
| Predicate | hasLegalProcessType |
P3010
|
FINISHED |
| Object | native title determination |
—
|
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: native title determination | Statement: [Gomeroi Native Title Applicant, hasLegalProcessType, native title determination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalProcessType Context triple: [Gomeroi Native Title Applicant, hasLegalProcessType, native title determination]
-
A.
hasLegalSystemType
Indicates that an entity possesses or is governed by a particular type or form of legal system.
-
B.
hasLegalThresholdType
Indicates that something is associated with a specific type or category of legal threshold that applies to it.
-
C.
hasLegalSubject
Indicates that an entity serves as the legal subject (e.g., rights-holder or obligated party) in a legal relationship or context.
-
D.
hasLegalProceeding
chosen
Indicates that there is a formal legal action, case, or proceeding involving the related entities.
-
E.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: May 3, 2026, 4:16 p.m.