Triple
T34325707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tasmanian Aboriginal people |
E880858
|
entity |
| Predicate | hasContemporaryLanguageUse |
P20092
|
FINISHED |
| Object | English |
E211
|
NE 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: English | Statement: [Tasmanian Aboriginal people, hasContemporaryLanguageUse, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContemporaryLanguageUse Context triple: [Tasmanian Aboriginal people, hasContemporaryLanguageUse, English]
-
A.
contemporaryUse
Indicates that something is currently used or practiced in the present time or modern context.
-
B.
statusInModernUsage
Indicates how the usage or relevance of something is currently regarded or applied in contemporary contexts.
-
C.
hasLinguisticLegacy
Indicates that one entity has left a lasting influence or enduring impact on the language, linguistic practices, or linguistic development associated with another entity.
-
D.
extantLanguage
chosen
Indicates that a language currently exists or is in active use, as opposed to being extinct or only historically attested.
-
E.
hasModernNameLanguage
Indicates that the modern name of an entity is expressed in a particular language.
- F. None of above.
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_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36f9c774a48190a019c4ac137eeae8 |
completed | June 20, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:58 a.m.