Triple
T29111030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cayo Levisa |
E736903
|
entity |
| Predicate | hasPortOfAccess |
P63633
|
FINISHED |
| Object | Palma Rubia |
—
|
NE NERFINISHED |
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: Palma Rubia | Statement: [Cayo Levisa, hasPortOfAccess, Palma Rubia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortOfAccess Context triple: [Cayo Levisa, hasPortOfAccess, Palma Rubia]
-
A.
hasNearbyPortAccess
chosen
Indicates that an entity is located close enough to a port to feasibly use it for access or transport.
-
B.
hasNearbyAccess
Indicates that one entity has convenient, close-proximity access to another resource, service, or location.
-
C.
hasBorderFacilityAccess
Indicates that an entity is permitted to enter, use, or operate within a designated border facility or checkpoint.
-
D.
hasPortOn
Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
-
E.
hasPortico
Indicates that one entity (typically a building or structure) features a portico as part of its architectural design.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: April 28, 2026, 11:18 a.m.