Triple
T24757277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yabem language |
E619324
|
entity |
| Predicate | hasLinguisticStudyBy |
P73410
|
FINISHED |
| Object | Otto Dempwolff |
—
|
NE NERFINISHED |
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: Otto Dempwolff | Statement: [Yabem language, hasLinguisticStudyBy, Otto Dempwolff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLinguisticStudyBy Context triple: [Yabem language, hasLinguisticStudyBy, Otto Dempwolff]
-
A.
hasPhonologicalStudyBy
chosen
Indicates that a phonological analysis or study has been conducted by a specified agent on a given linguistic subject.
-
B.
linguisticStudies
Indicates that an entity engages in or is associated with the academic study or analysis of language and its structure.
-
C.
hasLinguisticDocumentation
Indicates that there exists recorded linguistic information or documentation about the language or linguistic properties of the subject.
-
D.
hasLinguist
Indicates that an entity is associated with or possesses a linguist, typically as a member, employee, collaborator, or resource.
-
E.
hasLanguageOfStudy
Indicates that an entity studies or is engaged in learning a particular language.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 4:26 a.m.