Triple
T36801260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamatji |
E909326
|
entity |
| Predicate | hasAssociatedLanguageGroup |
P3349
|
FINISHED |
| Object | Wajarri language speakers |
—
|
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: Wajarri language speakers | Statement: [Yamatji, hasAssociatedLanguageGroup, Wajarri language speakers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedLanguageGroup Context triple: [Yamatji, hasAssociatedLanguageGroup, Wajarri language speakers]
-
A.
hasLanguageGroup
chosen
Indicates that an entity belongs to, is associated with, or is categorized under a particular language group.
-
B.
hasAssociatedLanguagePair
Indicates a relationship where a resource or entity is linked to a specific pair of languages, typically denoting a source and target language used together.
-
C.
hasRelatedLanguage
Indicates that one language is related to another through shared linguistic origins, features, or classification.
-
D.
hasRelatedGroup
Indicates that one group or collection is associated with another group or collection through some defined relationship or connection.
-
E.
hasEnglishGroupName
Indicates that an entity is associated with a group whose name is given in English.
- 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_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 3, 2026, 4:12 p.m.