Triple
T9461601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waigali |
E228157
|
entity |
| Predicate | documentationLanguageOf |
P42636
|
FINISHED |
| Object | local ethnographic knowledge |
—
|
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: local ethnographic knowledge | Statement: [Waigali, documentationLanguageOf, local ethnographic knowledge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentationLanguageOf Context triple: [Waigali, documentationLanguageOf, local ethnographic knowledge]
-
A.
languageOfDocumentation
chosen
Indicates the language in which the documentation for an entity is written or provided.
-
B.
languageOfCommunications
Indicates that a specified language is used as the medium for communications associated with an entity or interaction.
-
C.
governingLanguage
Indicates the language that holds official or authoritative status over a given entity, such as a region, organization, or document.
-
D.
languageProvision
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
-
E.
derivationLanguage
Indicates the language from which something (such as a word, term, or expression) is derived.
- 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fcc8b1881908aa6ee13ab195330 |
completed | April 1, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:52 p.m.