Triple
T6712354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoanya language |
E153175
|
entity |
| Predicate | isDocumentedAs |
P18402
|
FINISHED |
| Object | poorly attested |
—
|
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: poorly attested | Statement: [Hoanya language, isDocumentedAs, poorly attested]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDocumentedAs Context triple: [Hoanya language, isDocumentedAs, poorly attested]
-
A.
documentedUsing
Indicates that something is recorded, described, or specified by means of a particular document, tool, or documentation method.
-
B.
hasDocumentationAt
Indicates that something is documented or described in a specific document, file, or location.
-
C.
documentedThrough
Indicates that something is recorded, evidenced, or made known by means of a specific document or documentation process.
-
D.
hasLimitedDocumentation
chosen
Indicates that the subject is associated with documentation that is sparse, incomplete, or not sufficiently detailed.
-
E.
hasDocumentationStatus
Indicates the current state or condition of documentation associated with an entity, such as whether it exists, is complete, or is up to date.
- 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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d121a92c8190a03f384a8aba84da |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:07 p.m.