Triple
T33843006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Local Aboriginal Land Council |
E867403
|
entity |
| Predicate | languageGroupRegion |
P201612
|
FINISHED |
| Object | Eora |
—
|
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: Eora | Statement: [Metropolitan Local Aboriginal Land Council, languageGroupRegion, Eora]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageGroupRegion Context triple: [Metropolitan Local Aboriginal Land Council, languageGroupRegion, Eora]
-
A.
languageFamilyRegion
Indicates the geographic region or area in which a language family is predominantly found or historically associated.
-
B.
regionalLanguageGroup
chosen
Indicates that the related entities belong to the same group defined by shared or similar regional languages.
-
C.
subjectLanguageRegion
Indicates that the subject is associated with or uses a language specific to a particular geographic region.
-
D.
operatorLanguageRegion
Indicates the geographic region or locale in which an operator’s language is used or applicable.
-
E.
languageArea
Indicates the geographic or cultural region in which a particular language is used or predominantly spoken.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0039c2d5d48190b8ef2c7ef17d8dc5 |
completed | May 10, 2026, 7:54 a.m. |
| PD | Predicate disambiguation | batch_6a0038e525448190a4c815f51595e78d |
completed | May 10, 2026, 7:51 a.m. |
Created at: May 1, 2026, 1:47 a.m.