Triple
T6522504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Kaohsiung |
E151217
|
entity |
| Predicate | isMajorContainerPort |
P942
|
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: [Port of Kaohsiung, isMajorContainerPort, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorContainerPort Context triple: [Port of Kaohsiung, isMajorContainerPort, true]
-
A.
hasMajorPort
chosen
Indicates that a location possesses a primary, significant seaport used for major commercial or transportation activities.
-
B.
isMajorIndexOf
Indicates that one entity serves as the primary or major index reference for locating, organizing, or identifying another entity.
-
C.
isMajorHubType
Indicates that an entity functions as a primary or central hub within a larger network or system.
-
D.
isMajor
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
-
E.
isMajorTerminalOf
Indicates that one entity serves as a primary or main terminal (such as a key endpoint or hub) for another entity within a system or network.
- 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ad95c2c88190b800aaaa73f99210 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.