Triple
T9317583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Puerto Peñasco |
E224162
|
entity |
| Predicate | maritimeFacilityType |
P45226
|
FINISHED |
| Object | small regional port |
—
|
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: small regional port | Statement: [Port of Puerto Peñasco, maritimeFacilityType, small regional port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritimeFacilityType Context triple: [Port of Puerto Peñasco, maritimeFacilityType, small regional port]
-
A.
typeOfPortFacility
chosen
Indicates that one port facility is classified as a specific type or category of port facility in relation to another.
-
B.
berthType
Indicates the specific kind or category of berth associated with an entity, such as the type of sleeping or docking space provided.
-
C.
harborType
Indicates the specific kind or classification of a harbor associated with an entity.
-
D.
permanentPortFacilities
Indicates that an entity has fixed, long-term port infrastructure used for maritime operations, such as docks, piers, or terminals that are not temporary or mobile.
-
E.
navalBaseType
Indicates the specific category or classification of a naval base in terms of its role, function, or operational characteristics.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd358b66148190a918c107490c8406 |
completed | April 1, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:38 p.m.