Triple
T16777469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Ijaw |
E407764
|
entity |
| Predicate | usesLanguageVarieties |
P84576
|
FINISHED |
| Object | Eastern Ijaw dialects |
—
|
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: Eastern Ijaw dialects | Statement: [Eastern Ijaw, usesLanguageVarieties, Eastern Ijaw dialects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLanguageVarieties Context triple: [Eastern Ijaw, usesLanguageVarieties, Eastern Ijaw dialects]
-
A.
hasLinguisticVariety
chosen
Indicates that one entity possesses or exhibits a particular linguistic variety in relation to another entity or context.
-
B.
primaryLanguageVariety
Indicates the main dialect or specific variety of a language that an entity primarily uses.
-
C.
languageVariants
Indicates that one language form is a variant or alternative version of another language.
-
D.
workLanguageVariant
Indicates that one language variant of a work is related to another version of the same work, typically differing by language or localization.
-
E.
usesWorkingLanguagesOf
Indicates that one entity employs or operates using the working languages associated with another entity.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b212fc248190a8fe1124853bf16d |
completed | April 18, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.