Triple
T23741307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jarawan Bantu languages |
E586679
|
entity |
| Predicate | arePoorlyDocumented |
P18402
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Jarawan Bantu languages, arePoorlyDocumented, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arePoorlyDocumented Context triple: [Jarawan Bantu languages, arePoorlyDocumented, true]
-
A.
notWellDocumented
Indicates that the subject lacks sufficient, clear, or comprehensive documentation.
-
B.
hasLimitedDocumentation
chosen
Indicates that the subject is associated with documentation that is sparse, incomplete, or not sufficiently detailed.
-
C.
isPoorlyAttested
Indicates that there is limited, weak, or unreliable evidence or documentation supporting the existence, usage, or occurrence of the related item or relationship.
-
D.
areUnderdescribed
Indicates that the entities lack sufficient detail or explanation relative to what is needed or expected.
-
E.
isWidelyDocumented
Indicates that extensive and accessible documentation or records exist about the subject across multiple reputable sources.
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad61d908190a0a8493bbba95d49 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:11 p.m.