Triple
T7237315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riffian Berber |
E155261
|
entity |
| Predicate | hasISOCode |
P189
|
FINISHED |
| Object | rif |
E225395
|
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: rif | Statement: [Riffian Berber, hasISOCode, rif]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: rif Context triple: [Riffian Berber, hasISOCode, rif]
-
A.
Rif
Rif, also known as Rabbi Isaac Alfasi, was an 11th-century Talmudic scholar whose halachic digest of the Talmud became a foundational legal work that strongly shaped later Jewish law codes.
-
B.
Rif
chosen
Rif is a mountainous coastal region in northern Morocco known for its predominantly Amazigh (Berber) population and distinct cultural and historical identity.
-
C.
RIF
RIF (Rule Interchange Format) is a W3C standard designed to enable the exchange and interoperability of rules across different Semantic Web systems and rule engines.
-
D.
.rf
.rf is the Cyrillic country-code top-level domain representing the Russian Federation on the internet.
-
E.
ric
"ric" is an Old English name element meaning "ruler" or "power," commonly found in Anglo-Saxon personal names.
- 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_69c688143bfc81908d4176617735e601 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea355e888190a97de097158933ca |
completed | March 27, 2026, 8:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7cc381a4081909a8ea7ee02348328 |
completed | March 28, 2026, 12:40 p.m. |
Created at: March 27, 2026, 2:55 p.m.