Triple
T5066026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuta Lombok |
E114145
|
entity |
| Predicate | typicalVisitor |
P34539
|
FINISHED |
| Object | international 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: international tourists | Statement: [Kuta Lombok, typicalVisitor, international tourists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVisitor Context triple: [Kuta Lombok, typicalVisitor, international tourists]
-
A.
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).
-
B.
primaryVisitors
chosen
Indicates that certain entities are the main or most important visitors associated with another entity or context.
-
C.
visitorUse
Indicates that an entity is being used, accessed, or engaged with by a visitor or temporary user.
-
D.
visitorProfile
Indicates a relationship where a profile encapsulates information or attributes associated with a particular visitor.
-
E.
hasTypeOfVisitorExperience
Indicates that an entity is associated with a particular category or kind of visitor experience it provides or involves.
- 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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd749aceac8190817278266308fd64 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd715622b48190a3e8e49a5ef62b4a |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:38 p.m.