Triple
T18876423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | türbe of Hüma Hatun |
E461699
|
entity |
| Predicate | locatedInCemeteryOrComplex |
P91882
|
FINISHED |
| Object | complex of Muradiye in Bursa |
—
|
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: complex of Muradiye in Bursa | Statement: [türbe of Hüma Hatun, locatedInCemeteryOrComplex, complex of Muradiye in Bursa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCemeteryOrComplex Context triple: [türbe of Hüma Hatun, locatedInCemeteryOrComplex, complex of Muradiye in Bursa]
-
A.
locatedInCemetery
Indicates that one entity is situated within the grounds or area of a cemetery.
-
B.
cemeteryComplex
chosen
Indicates a relationship where a site or structure functions as, or is part of, a cemetery complex used for burials or memorials.
-
C.
isCemeteryFor
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
-
D.
hasNearbyCemetery
Indicates that one entity is located close to, or in the immediate vicinity of, a cemetery associated with another entity.
-
E.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c3cf0aa0819090991fc9e14910fb |
completed | April 20, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69e48d22dde8819093b1d963bd673365 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.