Triple
T7157959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gasthaus Wiesinger |
E166862
|
entity |
| Predicate | eventOccurredHereDate |
P51947
|
FINISHED |
| Object | 3 January 1903 |
—
|
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: 3 January 1903 | Statement: [Gasthaus Wiesinger, eventOccurredHereDate, 3 January 1903]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventOccurredHereDate Context triple: [Gasthaus Wiesinger, eventOccurredHereDate, 3 January 1903]
-
A.
eventOccurredAt
Indicates that a particular event took place at a specific time or location.
-
B.
eventDateAtLocation
chosen
Indicates that a specific event occurs on a particular date at a given location.
-
C.
dateOfRelatedEvent
Indicates that there is a specific date on which a related event associated with the subject occurs or occurred.
-
D.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
E.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
- 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_69c68887a5cc8190bec0ea96227164f7 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e8109a64819087e132d6d483c07d |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:47 p.m.