Triple
T26069392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bandar Lengeh |
E657497
|
entity |
| Predicate | isProvincialPortHub |
P161258
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bandar Lengeh, isProvincialPortHub, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isProvincialPortHub Context triple: [Bandar Lengeh, isProvincialPortHub, true]
-
A.
isPortOf
Indicates that one location or facility serves as a port or harbor for another place, entity, or transportation route.
-
B.
isPortTown
Indicates that a town is located on or near a navigable body of water and functions as a port for maritime or river transport and trade.
-
C.
isInlandPort
Indicates that a port facility is located inland, away from the open sea, typically on a river, canal, or lake, while still serving maritime or shipping functions.
-
D.
isHomePortOf
Indicates that a particular location serves as the primary base or port where a vessel or fleet is officially registered, stationed, or regularly returns.
-
E.
isMajorSeaport
Indicates that a location functions as a primary maritime port handling significant volumes of sea-based trade, transport, or shipping activity.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 26, 2026, 7:27 p.m.