Triple
T3906197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selimiye Mosque |
E87208
|
entity |
| Predicate | hasComplexElement |
P25619
|
FINISHED |
| Object | courtyard |
—
|
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: courtyard | Statement: [Selimiye Mosque, hasComplexElement, courtyard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComplexElement Context triple: [Selimiye Mosque, hasComplexElement, courtyard]
-
A.
hasComplex
Indicates that one entity possesses, is associated with, or is part of a larger composite structure or complex formed with another entity.
-
B.
hasComplexity
Indicates that something possesses a certain level or type of complexity, often in terms of structure, behavior, or difficulty.
-
C.
hasComplexOwnershipStructure
Indicates that an entity’s ownership is arranged through multiple layers, parties, or instruments such that control or equity interests are not straightforward to determine.
-
D.
hasFunctionInComplex
Indicates that an entity performs a specific functional role within a larger molecular or structural complex.
-
E.
hasSubcomponent
chosen
Indicates that one entity is a constituent part or component of another, larger entity.
- 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_69aed9424514819086e9c58adde6652d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75cff148190b6d5979d17fae085 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.