Triple
T11876956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | うめだスカイビル |
E282551
|
entity |
| Predicate | 観光地分類 |
P62013
|
FINISHED |
| Object | 大阪の観光名所 |
—
|
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: 大阪の観光名所 | Statement: [うめだスカイビル, 観光地分類, 大阪の観光名所]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 観光地分類 Context triple: [うめだスカイビル, 観光地分類, 大阪の観光名所]
-
A.
tourismType
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
B.
tourCategory
Indicates the classification or type of a tour (e.g., by theme, style, or purpose) that the tour belongs to.
-
C.
touristDesignation
chosen
Indicates that a place or entity has been formally identified or labeled as a tourist attraction or destination.
-
D.
tourismFeature
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
-
E.
tourismCharacteristic
Indicates that something has a specific feature, quality, or attribute relevant to tourism, such as what makes a place, service, or activity notable or suitable for tourists.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d39d2934819093b9f7006f45e5cb |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb272f88819090c37c944c5a60ab |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.