Triple
T3616548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surah al-Ahzab |
E76614
|
entity |
| Predicate | socialTheme |
P47748
|
FINISHED |
| Object | relations between men and women |
—
|
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: relations between men and women | Statement: [Surah al-Ahzab, socialTheme, relations between men and women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialTheme Context triple: [Surah al-Ahzab, socialTheme, relations between men and women]
-
A.
socialCategory
Indicates that an entity belongs to, or is classified within, a particular social group, class, or category.
-
B.
sharesThemeWith
chosen
Indicates that two entities are related by having the same or closely similar underlying theme or subject matter.
-
C.
socialCenter
Indicates that a place functions as a primary gathering point or hub for social interaction and community activities.
-
D.
socialCustom
Indicates a culturally shared, customary way of behaving or interacting that is expected or considered appropriate within a particular social group or context.
-
E.
socialSphere
Indicates the social environment or network within which an entity regularly interacts or maintains relationships.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc27c98088190a493c9eddf6b206a |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.