Triple
T9365904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irifiyen |
E225397
|
entity |
| Predicate | hasEthnonymForm |
P57538
|
FINISHED |
| Object | Irifiyen (plural) |
E225397
|
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: Irifiyen (plural) | Statement: [Irifiyen, hasEthnonymForm, Irifiyen (plural)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Irifiyen (plural) Context triple: [Irifiyen, hasEthnonymForm, Irifiyen (plural)]
-
A.
Irifiyen
chosen
Irifiyen is the endonym used by the Riffian people, an Amazigh (Berber) ethnic group indigenous to Morocco’s Rif region.
-
B.
Iferhounène
Iferhounène is a town and commune located in the mountainous Kabylie region of northern Algeria.
-
C.
Allifae
Allifae was an ancient Samnite town in south-central Italy, known from Roman-era sources and archaeological remains.
-
D.
Yffiniac
Yffiniac is a small commune in the Côtes-d'Armor department of Brittany in northwestern France.
-
E.
FFIRI
FFIRI is the commonly used abbreviation for the Football Federation Islamic Republic of Iran, the governing body for football in Iran.
- 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_69ca842cbddc819099d71ecec48cf9e5 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5041261c81909edab3b7fcd1fe22 |
completed | April 1, 2026, 5:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0f3fbe7d481909712531d907b77d8 |
completed | April 4, 2026, 11:20 a.m. |
Created at: March 30, 2026, 7:43 p.m.