Triple
T26977765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korandje people |
E679505
|
entity |
| Predicate | languageFamilyInfluence |
P18670
|
FINISHED |
| Object | Berber |
—
|
NE NERFINISHED |
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: Berber | Statement: [Korandje people, languageFamilyInfluence, Berber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageFamilyInfluence Context triple: [Korandje people, languageFamilyInfluence, Berber]
-
A.
languageInfluence
Indicates that one language has an effect on the development, usage, or characteristics of another language.
-
B.
influencedLanguageFamily
chosen
Indicates that one language family has had a significant impact on the development, structure, or usage of another language family.
-
C.
linguisticInfluence
Indicates that one entity has affected, shaped, or contributed to the language, style, or linguistic features of another entity.
-
D.
shareLanguageInfluence
Indicates that two entities affect or shape each other’s language use, development, or characteristics through mutual or shared influence.
-
E.
influencesLanguageOf
Indicates that one entity affects, shapes, or alters the language used by 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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: April 27, 2026, 6:43 a.m.