Triple
T22707533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yusuf Idris |
E561497
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Idris |
—
|
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: Idris | Statement: [Yusuf Idris, familyName, Idris]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Idris Context triple: [Yusuf Idris, familyName, Idris]
-
A.
Idris
chosen
Idris is an ancient prophet in Islamic tradition, often identified with the biblical Enoch and revered for his wisdom, piety, and early mastery of writing and knowledge.
-
B.
Idris
Idris is a functional programming language with full dependent types, designed for expressive type-driven development and interactive theorem proving.
-
C.
Idris
Idris is the central protagonist of Mary Shelley’s apocalyptic novel "The Last Man," navigating a world devastated by plague and societal collapse.
-
D.
Idris
Idris is a pivotal character in the Doctor Who episode "The Doctor's Wife," serving as the human embodiment of the Doctor's TARDIS.
-
E.
Idris I
Idris I was an 8th-century Arab leader and descendant of the Prophet Muhammad who established one of the earliest Islamic states in Morocco, laying the foundations of the Idrisid dynasty.
- 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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178cff7588190a40c8cef0f3cd44a |
completed | April 29, 2026, 3:19 a.m. |
Created at: April 17, 2026, 3:17 p.m.