Triple
T33769284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shrine of Mukhtar al-Thaqafi |
E865330
|
entity |
| Predicate | historicalEraReferenced |
P83770
|
FINISHED |
| Object | Umayyad period |
—
|
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: Umayyad period | Statement: [Shrine of Mukhtar al-Thaqafi, historicalEraReferenced, Umayyad period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEraReferenced Context triple: [Shrine of Mukhtar al-Thaqafi, historicalEraReferenced, Umayyad period]
-
A.
historicalEraOfNaming
Indicates the historical era or time period during which an entity received its name.
-
B.
historical era
chosen
Indicates the broad historical period or epoch during which an entity, event, or phenomenon took place or is associated.
-
C.
representedEra
Indicates the historical era or time period that something symbolizes, exemplifies, or stands for.
-
D.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
-
E.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or entity.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0018cf6ebc8190aee6288788d0067e |
completed | May 10, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_6a001855e8588190a65840485473cf8b |
completed | May 10, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:45 a.m.