Triple
T17294217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shush |
E419862
|
entity |
| Predicate | languageSpoken |
P151
|
FINISHED |
| Object | Luri |
E159563
|
NE 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: Luri | Statement: [Shush, languageSpoken, Luri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Luri Context triple: [Shush, languageSpoken, Luri]
-
A.
Luri
chosen
Luri is a Southwestern Iranian language spoken primarily by the Lur people in western and southwestern Iran.
-
B.
Luri
Luri is a commune in the Haute-Corse department on the island of Corsica in France, known for its scenic valley and coastal landscapes.
-
C.
Liluah
Liluah is a suburban locality in the Howrah district of West Bengal, India, known for its residential areas and railway facilities near Kolkata.
-
D.
Luro
Luro is an administrative post and rural area in eastern Timor-Leste known for its mountainous terrain and traditional villages.
-
E.
Lurya
Lurya is a variant form of the Jewish surname Luria, historically associated with prominent rabbinic and scholarly families.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e437869ec08190b4a63fb1ee6a71ee |
completed | April 19, 2026, 2:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0180d66bb8819086eb2c72b4dcbafb |
completed | May 11, 2026, 7:10 a.m. |
Created at: April 10, 2026, 5:40 a.m.