Triple
T38508453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yolŋu Sign Language |
E921832
|
entity |
| Predicate | communityWideKnowledge |
P70983
|
FINISHED |
| Object | many hearing Yolŋu people |
—
|
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: many hearing Yolŋu people | Statement: [Yolŋu Sign Language, communityWideKnowledge, many hearing Yolŋu people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communityWideKnowledge Context triple: [Yolŋu Sign Language, communityWideKnowledge, many hearing Yolŋu people]
-
A.
knows
Indicates that one entity has knowledge or awareness of another entity or piece of information.
-
B.
culturalKnowledge
chosen
Indicates that one entity possesses or conveys understanding of the customs, practices, values, or traditions associated with a particular culture.
-
C.
commonsCategory
Indicates that an entity is associated with a specific media or topic category on Wikimedia Commons.
-
D.
knowledgeExchange
Indicates a reciprocal sharing or transfer of knowledge, information, or expertise between entities.
-
E.
coreCommunity
Indicates that an entity belongs to the central or most essential group within a larger community.
- 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_69f76ea3c5448190aa7002fc1ba3f874 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.