Triple
T13451953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | إدريس |
E320627
|
entity |
| Predicate | يُعد_من_الأسماء_التقليدية |
P11158
|
FINISHED |
| Object | نعم |
—
|
LITERAL 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: نعم | Statement: [إدريس, يُعد_من_الأسماء_التقليدية, نعم]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: يُعد_من_الأسماء_التقليدية Context triple: [إدريس, يُعد_من_الأسماء_التقليدية, نعم]
-
A.
hasTraditionalName
Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
-
B.
traditionallyOneOf
chosen
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
-
C.
pairedTraditionalName
Indicates that two entities are associated as a traditional name pair, typically used together or in customary combination within a cultural or naming convention.
-
D.
isTraditional
Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
-
E.
isTraditionOf
Indicates that something is a customary practice, belief, or ritual associated with or belonging to a particular group, culture, or context.
- F. None of above.
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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaefae85481909e6a59797cbb25e7 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:41 p.m.