Triple
T3620002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ṭarābulus |
E76699
|
entity |
| Predicate | isSeaport |
P33212
|
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: [Ṭarābulus, isSeaport, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSeaport Context triple: [Ṭarābulus, isSeaport, true]
-
A.
hasSeaportStatus
chosen
Indicates that an entity possesses the status or designation of being a seaport or having seaport facilities.
-
B.
isCommercialPort
Indicates that a location functions as a port used for commercial or trade-related maritime activities.
-
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.
isBusiestSeaportIn
Indicates that a seaport handles the highest volume of traffic or activity compared to all other seaports within a specified region or area.
-
E.
isDeepWaterPort
Indicates that a port has sufficiently deep water to accommodate large, heavily loaded vessels without grounding.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2b85f6c819091000e231d9dac87 |
completed | March 8, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.