Triple
T28553783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | عزيز |
E722951
|
entity |
| Predicate | الهوية_الثقافية |
P122854
|
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.
culturalIdentifier
chosen
Indicates that one entity serves as a marker, label, or attribute that identifies or characterizes the cultural affiliation, background, or context of another entity.
-
B.
culturalIdentityTiedTo
Indicates that an entity’s cultural identity is closely connected or strongly associated with another specified entity or context.
-
C.
hasStrongCulturalIdentity
Indicates that an entity possesses a well-defined, deeply rooted, and strongly maintained sense of belonging to a particular culture or cultural tradition.
-
D.
culturalRegister
Indicates the level or type of formality, style, or social context in which language or behavior is used or appropriate.
-
E.
culturalType
Indicates the classification of something according to its cultural category, style, or tradition.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6504de65c81908ba7a633af156609 |
completed | May 2, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:44 a.m.