Triple
T22900194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gilimanuk Port |
E568288
|
entity |
| Predicate | hasCustomsAndSecurity |
P7852
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Gilimanuk Port, hasCustomsAndSecurity, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomsAndSecurity Context triple: [Gilimanuk Port, hasCustomsAndSecurity, yes]
-
A.
hasCustomsAndImmigration
chosen
Indicates that customs and immigration control services are present or provided at a given location or facility.
-
B.
hasCustomsCheckpoint
Indicates that a location or route includes an official customs inspection point where goods, vehicles, or people are checked for compliance with border regulations.
-
C.
hasNoCustomsControl
Indicates that there is no customs inspection or control applied between the related entities.
-
D.
hasBaggageCheck
Indicates that an entity provides or is associated with a service or facility for checking in baggage.
-
E.
hasCustomsAgency
Indicates that an entity is associated with or overseen by a specific customs agency responsible for regulating and controlling cross-border goods and related activities.
- 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_69e2458c23ec81908fa2570692c6614f |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1801626488190b7e8ce3301667987 |
completed | April 29, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:41 p.m.