Triple
T4018439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bandar Lampung |
E91220
|
entity |
| Predicate | gatewayFor |
P17407
|
FINISHED |
| Object | tourism to Lampung Province |
—
|
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 Lampung Province | Statement: [Bandar Lampung, gatewayFor, tourism to Lampung Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gatewayFor Context triple: [Bandar Lampung, gatewayFor, tourism to Lampung Province]
-
A.
servesAsGatewayTo
Indicates that one entity functions as an entry point, access route, or intermediary channel that enables reaching or connecting to another entity.
-
B.
gateWeight
Indicates the weight or importance assigned to a particular gate or transition within a process, model, or system.
-
C.
guestFlow
Indicates the movement or progression of guests through a space, process, or experience over time.
-
D.
touristGatewayTo
chosen
Indicates a relationship where one place serves as the primary access point or entry hub for tourists visiting another place.
-
E.
cityGateTo
Indicates a directional relationship where one location or path leads to or opens into a city gate.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaa984948190a252eaeb9dbae454 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.