Triple
T29364683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bezm-i Alem Valide Sultan Mosque |
E744682
|
entity |
| Predicate | hasImperialLoge |
P28777
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bezm-i Alem Valide Sultan Mosque, hasImperialLoge, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImperialLoge Context triple: [Bezm-i Alem Valide Sultan Mosque, hasImperialLoge, true]
-
A.
hasSultanLoge
chosen
Indicates that an entity possesses or includes a special seating area designated as the sultan’s box or royal loge.
-
B.
hasLoggia
Indicates that an entity (typically a building or dwelling) includes or is equipped with a loggia, i.e., a covered exterior gallery or open-sided room.
-
C.
hasImperialPalace
Indicates that an entity possesses or is the location of an official imperial palace.
-
D.
containsImperialRegalia
Indicates that one entity includes or holds the imperial regalia associated with another entity.
-
E.
usesImperialRegalia
Indicates that one entity employs or incorporates imperial regalia (such as crowns, scepters, or other sovereign insignia) in relation to another entity or context.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 28, 2026, 2:21 p.m.