Triple
T36801227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malgana language |
E909325
|
entity |
| Predicate | hasStatusInAustralia |
P33447
|
FINISHED |
| Object | Aboriginal heritage language |
—
|
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: Aboriginal heritage language | Statement: [Malgana language, hasStatusInAustralia, Aboriginal heritage language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStatusInAustralia Context triple: [Malgana language, hasStatusInAustralia, Aboriginal heritage language]
-
A.
isInAustralia
Indicates that the subject is located within the geographical boundaries of Australia.
-
B.
australiaSupports
Indicates that Australia provides assistance, endorsement, or backing to another entity or action.
-
C.
countrySpecificStatus
chosen
Indicates a status or condition that is defined or applied specifically in the context of a particular country.
-
D.
legalStatusInNSW
Indicates the legal status or standing of an entity under the laws and regulations specific to New South Wales (NSW).
-
E.
statusInUK
Indicates the legal or official status that an entity holds within the United Kingdom (e.g., immigration, residency, or authorization category).
- 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00532815c881908f10d9594458b3d7 |
completed | May 10, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_6a0052b9f030819081b8105bdcaf6d8f |
completed | May 10, 2026, 9:41 a.m. |
Created at: May 3, 2026, 4:12 p.m.