Triple
T34183374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | عثمان بن عفان |
E876887
|
entity |
| Predicate | تاريخ_الميلاد_التقريبي |
P160006
|
FINISHED |
| Object | حوالي 576 م |
—
|
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: حوالي 576 م | Statement: [عثمان بن عفان, تاريخ_الميلاد_التقريبي, حوالي 576 م]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: تاريخ_الميلاد_التقريبي Context triple: [عثمان بن عفان, تاريخ_الميلاد_التقريبي, حوالي 576 م]
-
A.
تاريخ الميلاد التقريبي
chosen
Indicates an approximate or estimated date of birth for an entity, rather than an exact known birth date.
-
B.
chronologicalPeriodApprox
Indicates that one entity is associated with a time period that is approximately, but not exactly, the same as the time period of another entity.
-
C.
تاريخ_الإنشاء_ميلادي
Indicates the Gregorian calendar date on which something was created or established.
-
D.
approximateBirthYear
Indicates that the associated year is an estimated or inferred value for when an entity was born, rather than an exact known birth year.
-
E.
approximateBirthCenturyBCE
Indicates that an entity’s birth is estimated to have occurred within a specified century before the Common Era (BCE), rather than on an exact year or date.
- 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_69f349ae640c8190b9cd220b5368d8b6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710075ce48190ad41ebd08e640c1e |
completed | May 3, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.