Triple
T35362658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuala Perlis Ferry Terminal |
E1021535
|
entity |
| Predicate | isMajorEmbarkationPointFor |
P195422
|
FINISHED |
| Object | 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: tourists | Statement: [Kuala Perlis Ferry Terminal, isMajorEmbarkationPointFor, tourists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorEmbarkationPointFor Context triple: [Kuala Perlis Ferry Terminal, isMajorEmbarkationPointFor, tourists]
-
A.
isMainHarbourOf
Indicates that a harbour serves as the primary or principal port facility for a specified location or region.
-
B.
isPortOfCallFor
Indicates that a location serves as a scheduled stop or destination for a ship, vehicle, or journey.
-
C.
isMajorSeaport
Indicates that a location functions as a primary maritime port handling significant volumes of sea-based trade, transport, or shipping activity.
-
D.
isHistoricPortOf
Indicates that a location served as a significant port for another place during a past historical period.
-
E.
hasMajorSeaPort
Indicates that a place possesses at least one significant seaport used for major maritime transport, trade, or shipping activities.
- F. None of above. chosen
Provenance (4 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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
| PDg | Predicate description generation | batch_69fdd07724f88190a33ec602642d2ea3 |
completed | May 8, 2026, noon |
Created at: May 3, 2026, 4:03 p.m.