Triple

T35552579
Position Surface form Disambiguated ID Type / Status
Subject Arakwal Indigenous Land Use Agreement area E1027402 entity
Predicate hasLandUseAgreementType P38198 FINISHED
Object Indigenous Land Use Agreement 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: Indigenous Land Use Agreement | Statement: [Arakwal Indigenous Land Use Agreement area, hasLandUseAgreementType, Indigenous Land Use Agreement]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLandUseAgreementType
Context triple: [Arakwal Indigenous Land Use Agreement area, hasLandUseAgreementType, Indigenous Land Use Agreement]
  • A. hasLandClaimAgreement
    Indicates that there exists a formal agreement granting or recognizing a party’s rights or claims to a specific piece of land.
  • B. hasLandUseCharacter
    Indicates that one entity possesses or is associated with a particular type or pattern of land use.
  • C. hasTypeOfAgreement chosen
    Indicates that one entity is associated with, or governed by, a specific category or type of agreement.
  • D. hasLandUseSystem
    Indicates that an entity is associated with or characterized by a particular system or pattern of land use.
  • E. landUseIncludes
    Indicates that a specified land area contains or permits the specified type(s) of land use within its boundaries.
  • 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_69f76e014fd481909e9f04ac603a2aa9 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69ff8ba3f8248190bbdf8e7ec2b35093 completed May 9, 2026, 7:31 p.m.
PD Predicate disambiguation batch_69ff8b41ba988190a7332e8317d10f09 completed May 9, 2026, 7:30 p.m.
Created at: May 3, 2026, 4:04 p.m.