Triple
T27036924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kağıthane Valley |
E681079
|
entity |
| Predicate | historicallyFrequentedBy |
P1097
|
FINISHED |
| Object | Ottoman court |
—
|
NE NERFINISHED |
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: Ottoman court | Statement: [Kağıthane Valley, historicallyFrequentedBy, Ottoman court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyFrequentedBy Context triple: [Kağıthane Valley, historicallyFrequentedBy, Ottoman court]
-
A.
historicallyInhabitedBy
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
-
B.
historicallySoughtBy
Indicates that one entity has been actively pursued, desired, or searched for by another entity in the past.
-
C.
historicalLocationOf
Indicates that a place served as a significant site or setting for an entity during a particular historical period or event.
-
D.
reputedToBeVisitedBy
Indicates that an entity is commonly believed or reported to be visited by another entity, without necessarily confirming that the visits actually occur.
-
E.
frequentlyVisitedBy
chosen
Indicates that an entity is regularly or often visited by another 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: April 27, 2026, 7:16 a.m.