Triple
T22951473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenje language |
E570029
|
entity |
| Predicate | alternativeName |
P39
|
FINISHED |
| Object | CiLenje |
—
|
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: CiLenje | Statement: [Lenje language, alternativeName, CiLenje]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CiLenje Context triple: [Lenje language, alternativeName, CiLenje]
-
A.
Lenje
chosen
Lenje is a Bantu language spoken primarily by the Lenje people of central Zambia.
-
B.
Klenje
Klenje is a town in Serbia located within the historic Mačva region.
-
C.
Lenjan
Lenjan is a city in Iran’s Isfahan Province, known for its location along the Zayandeh River and its role in the region’s industrial and agricultural activities.
-
D.
Ćići
Ćići are a historical population from the Istrian region, traditionally associated with the Istro-Romanian-speaking community and known for their distinct cultural and linguistic heritage.
-
E.
Cliza
Cliza is a small town and municipality in central Bolivia known for its agricultural activity and traditional festivals.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2459199d08190a8184ee2aa935842 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181a285448190a718734fe933d51a |
completed | April 29, 2026, 3:57 a.m. |
Created at: April 17, 2026, 3:46 p.m.