Triple
T11876958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | うめだスカイビル |
E282551
|
entity |
| Predicate | 観光客 |
P64169
|
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.
travelers
Indicates that one or more entities are engaged in the activity or role of traveling, typically moving from one place to another.
-
B.
visitor
Indicates that one entity is present at or attending another entity’s location, event, or context as a non-permanent guest.
-
C.
touristCharacter
Indicates that an entity has the role, behavior, or qualities characteristic of a tourist in relation to another entity or context.
-
D.
hasTouristVisits
chosen
Indicates that one entity experiences or records visits from tourists to another entity.
-
E.
hasVisitorsFrom
Indicates that an entity receives or has received visitors originating from another specified entity or location.
- 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.