Triple
T27655646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grotta di Nettuno |
E696982
|
entity |
| Predicate | boatDeparturesFrom |
P39763
|
FINISHED |
| Object | Alghero harbor |
—
|
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: Alghero harbor | Statement: [Grotta di Nettuno, boatDeparturesFrom, Alghero harbor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boatDeparturesFrom Context triple: [Grotta di Nettuno, boatDeparturesFrom, Alghero harbor]
-
A.
boatLaunch
Indicates the action or event of setting a boat into the water from land or a structure so it can begin operating or traveling.
-
B.
boatServiceFrom
chosen
Indicates that a boat transportation service operates starting from a specified location to one or more other locations.
-
C.
mooredAt
Indicates that one object, typically a vessel or floating structure, is secured or anchored at a specific location or facility.
-
D.
harbours
Indicates that one entity provides shelter, refuge, or concealment for another, often by keeping it safe or hidden.
-
E.
marineAttraction
Indicates a relationship where one entity serves as a point of interest or entertainment specifically related to marine life or the marine environment for another entity.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f631d8bb9881908a1b01a501d96cfc |
completed | May 2, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:34 p.m.