Triple
T14236043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rathausplatz |
E352878
|
entity |
| Predicate | hasMajorVisitorGroup |
P1284
|
FINISHED |
| Object | tourists |
—
|
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: tourists | Statement: [Rathausplatz, hasMajorVisitorGroup, tourists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorVisitorGroup Context triple: [Rathausplatz, hasMajorVisitorGroup, tourists]
-
A.
hasVisitorsFrom
Indicates that an entity receives or has received visitors originating from another specified entity or location.
-
B.
hasVisitorType
chosen
Indicates the type or category of visitor associated with an entity (e.g., guest, customer, tourist, patient).
-
C.
hasVisitorBuilding
Indicates that a particular building serves as a designated visitor facility or is intended for use by visitors.
-
D.
hasVisitorServices
Indicates that an entity provides services or facilities specifically intended for visitors or guests.
-
E.
hasVisitorPolicy
Indicates that an entity has an established policy governing the presence, behavior, or permissions of visitors.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62411c888190a154acd56fe3fcaf |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:07 a.m.