Triple
T25160491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Wiener Neustadt |
E626422
|
entity |
| Predicate | historicSee |
P110990
|
FINISHED |
| Object | Wiener Neustadt |
—
|
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: Wiener Neustadt | Statement: [Diocese of Wiener Neustadt, historicSee, Wiener Neustadt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicSee Context triple: [Diocese of Wiener Neustadt, historicSee, Wiener Neustadt]
-
A.
historicSeeOf
chosen
Indicates that a place serves or has served as the principal episcopal seat or central ecclesiastical jurisdiction of a bishop or similar religious authority.
-
B.
historicalSee
Indicates that one entity observed, encountered, or took visual notice of another entity in the past.
-
C.
otherHistoricSee
Indicates that an entity is associated with or linked to another historically significant site, event, or point of interest that can be seen or visited.
-
D.
historicFor
Indicates that something holds historical significance or importance specifically in relation to another entity.
-
E.
historicCore
Indicates that something is part of, located within, or associated with the original historic center or oldest developed area of a place.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 18, 2026, 6:31 a.m.