Triple
T24969170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bay of Paimpol |
E624831
|
entity |
| Predicate | maritimeHeritage |
P20564
|
FINISHED |
| Object | traditional fishing ports |
—
|
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: traditional fishing ports | Statement: [Bay of Paimpol, maritimeHeritage, traditional fishing ports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritimeHeritage Context triple: [Bay of Paimpol, maritimeHeritage, traditional fishing ports]
-
A.
hasMaritimeHeritage
chosen
Indicates that an entity possesses a historical, cultural, or traditional connection to maritime activities, seafaring, or the sea.
-
B.
navalHistory
Indicates a relationship where an entity is associated with the study, record, or events of naval or maritime military history.
-
C.
hasMaritimeMuseum
Indicates that one entity possesses, hosts, or includes a maritime museum as part of its features or facilities.
-
D.
seaVoyages
Indicates that one entity undertakes or is associated with journeys or travel by sea to or involving another entity.
-
E.
hullPreservation
Indicates the extent to which an object’s outer structure or surface has been maintained intact and protected from damage or deterioration.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6 a.m.