Triple
T26599652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mainau |
E667597
|
entity |
| Predicate | hasVisitorNumber |
P165860
|
FINISHED |
| Object | over 1 million visitors per year |
—
|
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: over 1 million visitors per year | Statement: [Mainau, hasVisitorNumber, over 1 million visitors per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisitorNumber Context triple: [Mainau, hasVisitorNumber, over 1 million visitors per year]
-
A.
hasVisitation
Indicates that one entity visits, or is allowed or scheduled to visit, another entity or location.
-
B.
hasVisitorBuilding
Indicates that a particular building serves as a designated visitor facility or is intended for use by visitors.
-
C.
hasVisitorType
Indicates the type or category of visitor associated with an entity (e.g., guest, customer, tourist, patient).
-
D.
hasVisitingTime
Indicates that there is a specified time period during which visits are allowed or scheduled for an entity.
-
E.
hasVisitorsFrom
Indicates that an entity receives or has received visitors originating from another specified entity or location.
- F. None of above. chosen
Provenance (4 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a9cb0bc8190bf8a9b319900bad5 |
completed | May 2, 2026, 8:12 p.m. |
Created at: April 27, 2026, 2:11 a.m.