Triple
T26551089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Busan city center |
E671679
|
entity |
| Predicate | majorVisitorType |
P34539
|
FINISHED |
| Object | local shoppers |
—
|
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: local shoppers | Statement: [Busan city center, majorVisitorType, local shoppers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorVisitorType Context triple: [Busan city center, majorVisitorType, local shoppers]
-
A.
primaryVisitors
chosen
Indicates that certain entities are the main or most important visitors associated with another entity or context.
-
B.
majorCustomer
Indicates that one entity is a primary or high-value customer of another entity, typically contributing a significant portion of business or revenue.
-
C.
typicalVisitType
Indicates the usual or most common category of visit associated with an entity or event.
-
D.
typicalVisitorOrigin
Indicates the usual geographic source or location from which visitors to a place, event, or entity most commonly come.
-
E.
visitorStatus
Indicates the current state or condition of an entity in its role as a visitor (e.g., whether they are active, pending, past, or otherwise classified in their visit).
- 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 27, 2026, 1:47 a.m.