Triple
T12225910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ekpeye |
E291350
|
entity |
| Predicate | nationalLanguageEnvironment |
P103878
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Ekpeye, nationalLanguageEnvironment, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalLanguageEnvironment Context triple: [Ekpeye, nationalLanguageEnvironment, English]
-
A.
nationalLanguageSpoken
Indicates that a particular language is officially recognized and commonly used as a national language within a given country or region.
-
B.
nationalLanguageStatus
Indicates that a language holds official or nationally recognized status within a country or political entity.
-
C.
nationalLanguageStandardizedIn
Indicates that a national language has been formally standardized or codified within a particular country or jurisdiction.
-
D.
nativeLanguage
Indicates the language that a person or entity originally learned and uses as their primary or first language.
-
E.
regionLanguage
Indicates that a particular language is used or officially recognized within a specific geographic region.
- 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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d920e312708190b4aede2e21f5f697 |
completed | April 10, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69d91c3d669c81908eea7ad61122d275 |
completed | April 10, 2026, 3:50 p.m. |
| PDg | Predicate description generation | batch_69d920c3dc9881908c396a4ab34f4836 |
completed | April 10, 2026, 4:09 p.m. |
Created at: April 8, 2026, 9:51 p.m.