Triple
T34326070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tasmanian Aboriginal Centre |
E880867
|
entity |
| Predicate | languageProgram |
P202227
|
FINISHED |
| Object | Palawa Kani language revival |
—
|
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: Palawa Kani language revival | Statement: [Tasmanian Aboriginal Centre, languageProgram, Palawa Kani language revival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageProgram Context triple: [Tasmanian Aboriginal Centre, languageProgram, Palawa Kani language revival]
-
A.
programLanguage
Indicates that an entity is implemented, written, or expressed using a particular programming language.
-
B.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
-
C.
languageOfProgramming
Indicates that one entity is a programming language used to implement, develop, or script the other entity.
-
D.
compilerLanguage
Indicates that one entity is the programming language in which a given compiler is implemented.
-
E.
languageOfCode
Indicates that a programming code artifact is written in, or uses, a particular programming language.
- F. None of above. chosen
Provenance (4 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_69f349b9cd508190a996a616903b3e6d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a006417d1f4819093b2da02dbf2ab22 |
completed | May 10, 2026, 10:55 a.m. |
| PD | Predicate disambiguation | batch_6a00634a7a748190ac4774493fce3d30 |
completed | May 10, 2026, 10:51 a.m. |
| PDg | Predicate description generation | batch_6a006416f78081909b6ef047c531158d |
completed | May 10, 2026, 10:55 a.m. |
Created at: May 1, 2026, 1:58 a.m.