Triple
T35185343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Traditional Owners of Kakadu |
E1015968
|
entity |
| Predicate | coManage |
P13336
|
FINISHED |
| Object | Kakadu National Park |
—
|
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: Kakadu National Park | Statement: [Traditional Owners of Kakadu, coManage, Kakadu National Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coManage Context triple: [Traditional Owners of Kakadu, coManage, Kakadu National Park]
-
A.
coManagedWith
chosen
Indicates that two or more entities share joint responsibility or authority in managing the same resource, project, or process.
-
B.
coManagementFocus
Indicates that two or more parties share responsibility and decision-making authority in managing a particular resource, project, or domain.
-
C.
managingCenter
Indicates that one entity serves as the administrative or coordinating center responsible for managing another entity or activity.
-
D.
managementSystem
Indicates a relationship where an entity oversees, organizes, and controls the operations, resources, or processes of another entity according to defined rules or procedures.
-
E.
managementIs
Indicates that one entity holds a managerial role, responsibility, or authority over another entity.
- 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.