Triple
T4989079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saranda |
E112082
|
entity |
| Predicate | hasHarborUse |
P12053
|
FINISHED |
| Object | military significance historically |
—
|
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: military significance historically | Statement: [Saranda, hasHarborUse, military significance historically]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHarborUse Context triple: [Saranda, hasHarborUse, military significance historically]
-
A.
hasHarbor
Indicates that a place possesses or contains a harbor for docking or sheltering vessels.
-
B.
hasHarborFeature
Indicates that something possesses or includes a specific harbor-related characteristic, structure, or facility.
-
C.
hasHarborOpened
Indicates that a harbor has been officially opened and is available for use or operation.
-
D.
harbourUse
chosen
Indicates how a harbour is used or purposed, such as for specific activities, functions, or types of maritime operations.
-
E.
hasNearbyHarbor
Indicates that one location has a harbor situated close to it in geographic proximity.
- 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_69bd441be7bc8190b530362d427b97d2 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71492dec8190af4c27a3043b35cc |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:34 p.m.