Triple
T33457549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | الزمخشري |
E856817
|
entity |
| Predicate | الانتماء_الحضاري |
P156164
|
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.
culturalIdentityTiedTo
chosen
Indicates that an entity’s cultural identity is closely connected or strongly associated with another specified entity or context.
-
B.
culturalIdentifier
Indicates that one entity serves as a marker, label, or attribute that identifies or characterizes the cultural affiliation, background, or context of another entity.
-
C.
nationalIdentityBasis
Indicates that one entity serves as the defining basis or foundation for the national identity of another entity.
-
D.
culturalComplex
Indicates a relationship where multiple cultural elements, practices, or traits are interconnected and function together as a unified cultural system or pattern.
-
E.
ethnicIdentityOf
Indicates that one entity is the ethnic identity or affiliation possessed by another 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_69f3497281a08190b4705de0b5f26ba7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:37 a.m.