Triple
T26181669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naguib Mahfouz’s Miramar universe |
E654700
|
entity |
| Predicate | centralSetting |
P4751
|
FINISHED |
| Object | Pension Miramar |
—
|
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: Pension Miramar | Statement: [Naguib Mahfouz’s Miramar universe, centralSetting, Pension Miramar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralSetting Context triple: [Naguib Mahfouz’s Miramar universe, centralSetting, Pension Miramar]
-
A.
secondarySetting
Indicates that an entity serves as an additional or supporting setting context for another entity, rather than being the primary setting.
-
B.
coversSetting
Indicates that one entity includes or addresses a particular setting or context within its scope.
-
C.
primarySetting
Indicates that one entity serves as the main or central location, context, or environment in which the other entity’s events or activities primarily take place.
-
D.
primarySettingFeature
Indicates that a particular feature is the main or defining characteristic of a setting.
-
E.
centralIn
chosen
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 26, 2026, 8:40 p.m.