Triple
T25054965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lelemi people |
E627491
|
entity |
| Predicate | nativeNameOfLanguage |
P52154
|
FINISHED |
| Object | Lelemi |
—
|
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: Lelemi | Statement: [Lelemi people, nativeNameOfLanguage, Lelemi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeNameOfLanguage Context triple: [Lelemi people, nativeNameOfLanguage, Lelemi]
-
A.
nativeLanguageFamilyName
Indicates the name of the language family to which an entity’s native language belongs.
-
B.
localLanguageName
chosen
Indicates the name of a language as it is written or referred to in its own local or native form.
-
C.
alternateLanguageName
Indicates that an entity has an additional name or label in a different language from its primary or default name.
-
D.
isoLanguageOf
Indicates that one entity is the ISO 639 language code corresponding to the language represented by the other entity.
-
E.
standardLanguageOf
Indicates that one entity serves as the officially recognized or commonly used standard language for another entity (such as a country, region, or organization).
- 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_69e2ff2c45f48190afa28369f1df6786 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46d3f35848190b56a4373c97a7d64 |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 6:09 a.m.