Triple
T26188769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Königswinter |
E654904
|
entity |
| Predicate | hasConferenceVenue |
P112843
|
FINISHED |
| Object | Hotel Petersberg |
—
|
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: Hotel Petersberg | Statement: [Königswinter, hasConferenceVenue, Hotel Petersberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConferenceVenue Context triple: [Königswinter, hasConferenceVenue, Hotel Petersberg]
-
A.
hasConference
Indicates that an entity organizes, hosts, or is associated with a specific conference.
-
B.
hasConferenceSpace
Indicates that an entity provides or includes dedicated space suitable for holding conferences, meetings, or similar gatherings.
-
C.
hasVenueIn
Indicates that an event, activity, or occurrence takes place at a specific venue located within a particular geographic area or location.
-
D.
hasConferenceType
Indicates that an entity is associated with or classified by a specific type or category of conference.
-
E.
hasVenueFor
chosen
Indicates that one entity provides or serves as the location or setting where an event, activity, or function takes place for 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: April 26, 2026, 8:43 p.m.