Triple
T21659376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IDRIS |
E534553
|
entity |
| Predicate | acronym |
P43
|
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: [IDRIS, acronym, IDRIS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IDRIS Context triple: [IDRIS, acronym, IDRIS]
-
A.
IDRIS
chosen
IDRIS is a French national high-performance computing center that provides supercomputing resources and support for scientific research.
-
B.
Idris Alooma
Idris Alooma was a powerful 16th-century ruler of the Bornu Empire known for his military conquests, administrative and Islamic reforms, and expansion of trans-Saharan trade.
-
C.
Idre
Idre is a village and popular outdoor tourism destination in Dalarna County, Sweden, known for its nearby ski resort and mountain landscapes.
-
D.
إدريس
إدريس هو اسم علم عربي يُستخدم للذكور وله جذور دينية وتاريخية في الثقافة الإسلامية.
-
E.
Iddo
Iddo is a biblical figure mentioned in the Old Testament, known primarily as an ancestor of the prophet Zechariah and sometimes identified as a seer or priest.
- 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_69e0c467e1f48190af2650b19175abc4 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef6c06844c81909b9c91e02fa4e6e1 |
completed | April 27, 2026, 2 p.m. |
Created at: April 16, 2026, 6:36 p.m.