Triple
T21588115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umbundu language |
E532704
|
entity |
| Predicate | hasStatusInAngola |
P49093
|
FINISHED |
| Object | major national language |
—
|
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: major national language | Statement: [Umbundu language, hasStatusInAngola, major national language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStatusInAngola Context triple: [Umbundu language, hasStatusInAngola, major national language]
-
A.
statusInAngola
chosen
Indicates the legal, social, or operational standing or condition that something or someone has within the context of Angola.
-
B.
statusInEquatorialGuinea
Indicates the legal, social, or functional standing or condition that something or someone has within the context of Equatorial Guinea.
-
C.
areaRankInAngola
Indicates the relative position of an entity in a ranking ordered by its area size within Angola.
-
D.
legalStatusInPortugal
Indicates the legal status or classification that an entity holds specifically within the jurisdiction of Portugal.
-
E.
statusInGhana
Indicates the legal, social, or official standing or condition an entity holds within the context of Ghana.
- 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_69e0c46251648190876f0427cf2d321b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeeb621ab88190a33a943424ffb306 |
completed | April 27, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:31 p.m.