Triple
T36353534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vestisches Museum |
E895273
|
entity |
| Predicate | hasMainTerritoryOfInterest |
P25176
|
FINISHED |
| Object | Vest Recklinghausen district |
E738221
|
NE 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: Vest Recklinghausen district | Statement: [Vestisches Museum, hasMainTerritoryOfInterest, Vest Recklinghausen district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainTerritoryOfInterest Context triple: [Vestisches Museum, hasMainTerritoryOfInterest, Vest Recklinghausen district]
-
A.
hasAreaOfInterest
chosen
Indicates that an entity possesses or is associated with a particular area of interest or focus.
-
B.
hasMainPlace
Indicates that one entity is designated as the primary or central location associated with another entity.
-
C.
isTouristDestination
Indicates that a place is recognized as a location people commonly visit for leisure, sightseeing, or travel.
-
D.
containsTouristArea
Indicates that a place or region includes within its boundaries an area primarily designated or recognized for tourism activities.
-
E.
hasGoalForTourists
Indicates that something is intended or designed to achieve a specific objective or benefit for tourists.
- F. None of above.
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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0332a08b48819094aaed6e04a36886 |
completed | May 12, 2026, 2:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39b4290b148190b1890397fd8ea8da |
completed | June 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_6a0331998a688190b5d919697d4231ac |
completed | May 12, 2026, 1:56 p.m. |
Created at: May 3, 2026, 4:09 p.m.