Triple
T14835129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Porto Praya |
E348810
|
entity |
| Predicate | harborStatus |
P116018
|
FINISHED |
| Object | neutral harbor |
—
|
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: neutral harbor | Statement: [Battle of Porto Praya, harborStatus, neutral harbor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: harborStatus Context triple: [Battle of Porto Praya, harborStatus, neutral harbor]
-
A.
harborManagedBy
Indicates that the operation, administration, or oversight of a harbor is carried out by a specified managing entity.
-
B.
harborDescription
Indicates that one entity serves as a harbor or safe anchorage location for another entity, typically providing shelter, docking, or protection.
-
C.
harborOwnership
Indicates that one entity possesses legal or recognized ownership rights over a harbor or port facility.
-
D.
harborRole
Indicates that an entity serves in a particular capacity, function, or role within a specified context or relationship.
-
E.
harbor
Indicates providing shelter, protection, or refuge for someone or something, often by keeping them in a safe or hidden place.
- 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded076ac9c8190a05cabec5e87d207 |
completed | April 14, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de90806f3881908fcbfec5bd4ab4d2 |
completed | April 14, 2026, 7:07 p.m. |
Created at: April 10, 2026, 1:52 a.m.