Triple
T20322026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riad Seif |
E492228
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Seif |
—
|
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: Seif | Statement: [Riad Seif, familyName, Seif]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Seif Context triple: [Riad Seif, familyName, Seif]
-
A.
Seif
chosen
Seif is a family name most notably associated with Riad Seif, a prominent Syrian businessman and opposition politician.
-
B.
Zul Kifl
Zul Kifl is an Islamic prophet or righteous figure mentioned briefly in the Qur’an, traditionally identified by some scholars with the biblical Ezekiel.
-
C.
Sulem
Sulem is a modern locality believed by some scholars to correspond to the ancient biblical town of Shunem in present-day Israel.
-
D.
Moneer
Moneer is a given name, typically an alternative transliteration of the Arabic name Munir, meaning "bright" or "illuminating."
-
E.
Taher
Taher is a town and commune in northeastern Algeria, serving as an important local center within Jijel Province.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778c4430819083b17da5067b88ef |
completed | April 20, 2026, 6:59 p.m. |
Created at: April 16, 2026, 11:20 a.m.