Triple
T26383507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoanya people |
E663206
|
entity |
| Predicate | languageDocumentation |
P123492
|
FINISHED |
| Object | limited linguistic records |
—
|
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: limited linguistic records | Statement: [Hoanya people, languageDocumentation, limited linguistic records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageDocumentation Context triple: [Hoanya people, languageDocumentation, limited linguistic records]
-
A.
languageOfDocumentation
Indicates the language in which the documentation for an entity is written or provided.
-
B.
linguisticDocumentationType
chosen
Indicates the specific kind or category of documentation associated with a linguistic resource or activity.
-
C.
languageNote
Indicates a note or comment providing additional information or clarification about the language used or associated with an entity or resource.
-
D.
languageStatusDocumented
Indicates that the language’s existence, features, or usage have been formally recorded or described in documentation.
-
E.
languageAssistanceBasis
Indicates the basis or grounds on which language assistance is provided or justified in a given context.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 26, 2026, 11:20 p.m.