Triple
T22464418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merapi lava tour area |
E555312
|
entity |
| Predicate | commonVisitorOrigin |
P74830
|
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: [Merapi lava tour area, commonVisitorOrigin, domestic tourists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonVisitorOrigin Context triple: [Merapi lava tour area, commonVisitorOrigin, domestic tourists]
-
A.
typicalVisitorOrigin
chosen
Indicates the usual geographic source or location from which visitors to a place, event, or entity most commonly come.
-
B.
hasPrimaryVisitorOrigin
Indicates that an entity’s main or most common source location of its visitors is a specified place.
-
C.
registrationOrigin
Indicates the source or context from which a registration event was initiated or created.
-
D.
visitorIs
Indicates that one entity is acting in the role or capacity of a visitor with respect to another entity.
-
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_69e11e51fdec8190adfdf9f8a6362221 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b82549c8190943c0940bb90bafc |
completed | April 29, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.