Triple
T16392927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | İskele Camii |
E398099
|
entity |
| Predicate | hasComplexPart |
P31120
|
FINISHED |
| Object | madrasah |
—
|
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: madrasah | Statement: [İskele Camii, hasComplexPart, madrasah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComplexPart Context triple: [İskele Camii, hasComplexPart, madrasah]
-
A.
hasComplexPoints
Indicates that something possesses or includes points that are intricate, detailed, or composed of multiple interconnected parts.
-
B.
hasComplex
chosen
Indicates that one entity possesses, is associated with, or is part of a larger composite structure or complex formed with another entity.
-
C.
hasRealComponents
Indicates that an entity possesses components or parts whose values are real (non-complex) numbers.
-
D.
imaginaryPart
Indicates the relationship that maps a complex-valued entity to the value of its imaginary component.
-
E.
isTotallyComplex
Indicates that something possesses a level of complexity that is complete, multifaceted, and not reducible to simpler or purely real/straightforward components.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e326447a7481909feac905edc707ec |
completed | April 18, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.