Triple
T25041371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yorta Yorta Nation |
E627120
|
entity |
| Predicate | agreementFocus |
P38485
|
FINISHED |
| Object | joint management of Barmah–Millewa forest areas |
—
|
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: joint management of Barmah–Millewa forest areas | Statement: [Yorta Yorta Nation, agreementFocus, joint management of Barmah–Millewa forest areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agreementFocus Context triple: [Yorta Yorta Nation, agreementFocus, joint management of Barmah–Millewa forest areas]
-
A.
aimOfAgreement
chosen
Indicates the intended purpose or objective that an agreement is designed to achieve.
-
B.
agreement
Indicates that two or more parties mutually consent to and accept shared terms, conditions, or understandings.
-
C.
argumentFocus
Indicates that a particular argument within a relation or event is being highlighted as the primary focus or point of emphasis.
-
D.
agreementOutcome
Indicates the result or consequence that follows from reaching or failing to reach an agreement between parties.
-
E.
involvedAgreement
Indicates that an entity participates in, is a party to, or is otherwise associated with a specific agreement or contract.
- 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_69e2ff2b4c80819087c916b2b16241b9 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4530aeb7c8190af81f3329e8acf45 |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:08 a.m.