Triple
T27507560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gran Tarajal port |
E694318
|
entity |
| Predicate | isMinorPortRelativeTo |
P162459
|
FINISHED |
| Object | Puerto del Rosario port |
—
|
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: Puerto del Rosario port | Statement: [Gran Tarajal port, isMinorPortRelativeTo, Puerto del Rosario port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMinorPortRelativeTo Context triple: [Gran Tarajal port, isMinorPortRelativeTo, Puerto del Rosario port]
-
A.
isPortFor
Indicates that one entity serves as a port, interface, or connection point for another entity.
-
B.
isMinor
Indicates that one entity is legally or socially considered underage or not yet an adult in relation to a given context.
-
C.
isInPort
Indicates that an entity (such as a vessel or vehicle) is currently located within or docked at a specific port.
-
D.
isMajorSeeWithin
Indicates that one entity is the primary or most significant location or area encompassed within the boundaries of another entity.
-
E.
isMajorFor
Indicates that one entity serves as the primary field of academic specialization (major) for another entity, typically a student.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62ef65ca88190b3e3b1c91d668843 |
completed | May 2, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 1:14 p.m.