Triple
T29028089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wiener Salonblatt |
E737650
|
entity |
| Predicate | primaryCityOfPublication |
P136244
|
FINISHED |
| Object | Vienna |
—
|
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: Vienna | Statement: [Wiener Salonblatt, primaryCityOfPublication, Vienna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCityOfPublication Context triple: [Wiener Salonblatt, primaryCityOfPublication, Vienna]
-
A.
primaryCity
Indicates that one city serves as the main or most important city associated with a given region, entity, or context.
-
B.
primaryLocationCity
chosen
Indicates the city that serves as the main or primary location associated with the subject.
-
C.
primaryCityDocumented
Indicates that a city is recorded or designated as the main or principal city associated with a given entity or context.
-
D.
principalCityOf
Indicates that a city serves as the main or most important city (often administrative, economic, or cultural center) of a specified region or area.
-
E.
primaryUseCity
Indicates that a city is the main or principal location where something (such as a service, facility, or entity) is primarily used or operates.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a00ac5654a0819090701f61a5802d64 |
completed | May 10, 2026, 4:03 p.m. |
| PD | Predicate disambiguation | batch_6a00ab94b5e881909e15d1342e5f43be |
completed | May 10, 2026, 4 p.m. |
Created at: April 28, 2026, 9:53 a.m.