Triple
T35185348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Traditional Owners of Kakadu |
E1015968
|
entity |
| Predicate | areConsultedOn |
P20388
|
FINISHED |
| Object | Park management plans |
—
|
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: Park management plans | Statement: [Traditional Owners of Kakadu, areConsultedOn, Park management plans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areConsultedOn Context triple: [Traditional Owners of Kakadu, areConsultedOn, Park management plans]
-
A.
consultsOn
Indicates that one entity provides expert advice, guidance, or professional input to another entity regarding a specific subject, project, or decision.
-
B.
consulted
chosen
Indicates that one entity sought advice, information, or guidance from another entity.
-
C.
consultedWhen
Indicates that one entity is consulted at a particular time or under specific temporal conditions relative to another entity or event.
-
D.
mayConsultWith
Indicates that one entity is permitted or allowed to seek advice, guidance, or professional input from another entity.
-
E.
requiresConsultationWith
Indicates that performing an action or making a decision depends on first obtaining input, approval, or advice from a specified party.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78dc196708190a1a1cf7b9068e1cd |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.