Triple
T35893396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Istanbuler Mitteilungen |
E1038146
|
entity |
| Predicate | primaryGeographicCoverage |
P199907
|
FINISHED |
| Object | Istanbul |
E4825
|
NE 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: Istanbul | Statement: [Istanbuler Mitteilungen, primaryGeographicCoverage, Istanbul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryGeographicCoverage Context triple: [Istanbuler Mitteilungen, primaryGeographicCoverage, Istanbul]
-
A.
geographicCoverageType
Indicates the type or nature of the geographic area that something covers or applies to.
-
B.
hasPrimaryGeographicScope
chosen
Indicates that an entity is associated with a main or principal geographic area in which it is focused, applicable, or relevant.
-
C.
regionCoverage
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
D.
geographicReception
Indicates the geographic area or location where something (such as a work, message, or signal) is received, experienced, or has effect.
-
E.
geographicAreaOfSupport
Indicates the geographic region or area within which support, assistance, or services are provided or applicable.
- F. None of above.
Provenance (4 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_69f76e2190f88190beb2eed798a4ef01 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39f8f0adbc819085f16fe3a2324a00 |
completed | June 23, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.