Triple
T5568017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aboriginal and Torres Strait Islander cultures |
E145926
|
entity |
| Predicate | hasContemporaryIssue |
P40848
|
FINISHED |
| Object | land rights |
—
|
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: land rights | Statement: [Aboriginal and Torres Strait Islander cultures, hasContemporaryIssue, land rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContemporaryIssue Context triple: [Aboriginal and Torres Strait Islander cultures, hasContemporaryIssue, land rights]
-
A.
modernIssue
chosen
Indicates that the subject is a contemporary or current-day issue affecting the object or broader context.
-
B.
hasContemporaryActivity
Indicates that two activities occur during the same time period or overlap in time.
-
C.
currentIssue
Indicates that an entity is the presently relevant or active issue in a given context or discussion.
-
D.
involvesIssue
Indicates that an action, event, or entity is related to, concerns, or includes a particular issue.
-
E.
hasNotableIssue
Indicates that an entity is associated with a significant problem, concern, or defect that is noteworthy or exceptional compared to typical cases.
- 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_69c008fdae24819081aa002ad99cd966 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0203631c881908978d51e99155014 |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b12826c8190969a584d0f53aa44 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.