Triple
T3851552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yeşil Türbe |
E85304
|
entity |
| Predicate | upperLevelUse |
P44317
|
FINISHED |
| Object | symbolic sarcophagi hall |
—
|
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: symbolic sarcophagi hall | Statement: [Yeşil Türbe, upperLevelUse, symbolic sarcophagi hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperLevelUse Context triple: [Yeşil Türbe, upperLevelUse, symbolic sarcophagi hall]
-
A.
lowerLevelUsedFor
Indicates that a lower-level component, resource, or abstraction is utilized to implement, support, or realize the functionality of a higher-level one.
-
B.
hasUpperFloorUse
chosen
Indicates that an entity’s upper floor is assigned or designated for a particular use or function.
-
C.
hasUpperTier
Indicates that one entity occupies a higher or superior level, rank, or layer in a hierarchical structure relative to another entity.
-
D.
above
Indicates that one entity is positioned higher than another along a vertical axis, without implying direct contact.
-
E.
expandedUseOf
Indicates that something is being applied, implemented, or utilized more broadly or extensively than before.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeebd0feb081909cc1d5bf41e4acd6 |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee750377c8190af70c79768c0edd8 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.