Triple
T7750413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nemocón salt mine |
E175743
|
entity |
| Predicate | openedToPublicAsTouristAttraction |
P17187
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Nemocón salt mine, openedToPublicAsTouristAttraction, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedToPublicAsTouristAttraction Context triple: [Nemocón salt mine, openedToPublicAsTouristAttraction, 20th century]
-
A.
tourOpened
Indicates that a tour has begun or been made available for participation or viewing.
-
B.
openedToPublicAsMonument
Indicates that something was officially made accessible to the general public in the capacity or status of a monument.
-
C.
touristAccess
chosen
Indicates that a place or resource is available for use or visitation by tourists.
-
D.
hasTouristAttractionRole
Indicates that an entity serves in the capacity or function of a tourist attraction for another entity (such as a place, organization, or area).
-
E.
openedToPublicAsMuseum
Indicates that a place or building was made accessible to the general public specifically in the capacity of a museum.
- 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_69c69960b3588190a53aa590d31d9544 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c705257ca08190a78c592a1e616da8 |
completed | March 27, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69c7016df2b08190b2330a2010691431 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:08 p.m.