Triple
T38098776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurazukuri Street |
E951317
|
entity |
| Predicate | mainVisitorOrigin |
P141040
|
FINISHED |
| Object | domestic tourists |
—
|
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: domestic tourists | Statement: [Kurazukuri Street, mainVisitorOrigin, domestic tourists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainVisitorOrigin Context triple: [Kurazukuri Street, mainVisitorOrigin, domestic tourists]
-
A.
typicalVisitorOrigin
Indicates the usual geographic source or location from which visitors to a place, event, or entity most commonly come.
-
B.
hasPrimaryVisitorOrigin
chosen
Indicates that an entity’s main or most common source location of its visitors is a specified place.
-
C.
isMainVisitorHubOf
Indicates that a location serves as the primary central hub or focal point for visitors to a particular place, site, or area.
-
D.
visitorIs
Indicates that one entity is acting in the role or capacity of a visitor with respect to another entity.
-
E.
primaryVisitors
Indicates that certain entities are the main or most important visitors associated with another entity or context.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.