Triple
T20143499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lembar |
E491234
|
entity |
| Predicate | seaConnectionSupports |
P49633
|
FINISHED |
| Object | tourism to Lombok |
—
|
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: tourism to Lombok | Statement: [Lembar, seaConnectionSupports, tourism to Lombok]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaConnectionSupports Context triple: [Lembar, seaConnectionSupports, tourism to Lombok]
-
A.
seaConnection
chosen
Indicates a relationship where two places are connected or accessible to each other via the sea, such as by maritime routes or coastal adjacency.
-
B.
hasMaritimeConnection
Indicates a relationship in which an entity is linked to seas, oceans, or maritime activities, such as shipping, navigation, or coastal operations.
-
C.
touchesSea
Indicates that one entity is in direct physical contact with the sea or coastline of another entity.
-
D.
hasTidalConnection
Indicates that one entity is linked to another through the movement, influence, or exchange of tidal waters.
-
E.
connectsBodyOfWater
Indicates a relationship where one entity serves as a link or passage between two bodies of water, allowing them to be joined or interact.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6679cbc388190bb2b444a69a597a6 |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:33 p.m.