Triple
T11575198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bena–Mboi languages |
E274484
|
entity |
| Predicate | areUnderdescribed |
P100401
|
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: [Bena–Mboi languages, areUnderdescribed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areUnderdescribed Context triple: [Bena–Mboi languages, areUnderdescribed, true]
-
A.
notDescribedAs
Indicates that an entity is explicitly not characterized, labeled, or referred to using a particular description or term.
-
B.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
C.
moreAccuratelyDescribedAs
Indicates that one entity is a more precise or correct description, label, or characterization of another entity than an alternative.
-
D.
under
Indicates that one entity is positioned below or beneath another entity, often implying vertical alignment or coverage.
-
E.
laterDescribedAs
Indicates that an entity is referred to or characterized by a particular description or label at a later time.
- F. None of above. chosen
Provenance (4 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89048120c81908258f984711f7dd4 |
completed | April 10, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:38 p.m.