Triple
T4055593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman culture |
E84685
|
entity |
| Predicate | hasSocialPractice |
P53044
|
FINISHED |
| Object | patronage of waqf |
—
|
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: patronage of waqf | Statement: [Ottoman culture, hasSocialPractice, patronage of waqf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSocialPractice Context triple: [Ottoman culture, hasSocialPractice, patronage of waqf]
-
A.
hasSocialDimension
Indicates that the relationship, attribute, or phenomenon involves social aspects, interactions, or implications among individuals or groups.
-
B.
isPracticedBy
Indicates that an activity, skill, or discipline is regularly performed or carried out by a particular entity.
-
C.
hasSocialGroup
Indicates that an entity belongs to, is associated with, or participates in a particular social group or community.
-
D.
sociallyIntegratedWith
Indicates that two entities are connected through meaningful social relationships, interactions, or participation within the same social context or community.
-
E.
hadPractice
Indicates that an entity engaged in or participated in a practice session or rehearsal.
- F. None of above. chosen
Provenance (4 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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbabec608190a35d39d3d03b928b |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef90249e4819095e9e043bc4aa9a6 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aef9fcb31c819098d5287b6fc84f4e |
completed | March 9, 2026, 4:49 p.m. |
Created at: March 9, 2026, 3:38 p.m.