Triple
T37700927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detached Mole |
E939057
|
entity |
| Predicate | isMajorBreakwaterOf |
P34503
|
FINISHED |
| Object | Gibraltar Harbour |
—
|
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: Gibraltar Harbour | Statement: [Detached Mole, isMajorBreakwaterOf, Gibraltar Harbour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorBreakwaterOf Context triple: [Detached Mole, isMajorBreakwaterOf, Gibraltar Harbour]
-
A.
hasBreakwater
chosen
Indicates that a structure or location is equipped with or associated with a breakwater that provides protection from waves or erosion.
-
B.
isMajorDamOf
Indicates that one dam is the primary or most significant dam associated with a particular river, reservoir, or water system.
-
C.
isMajorBeachOf
Indicates that a beach is one of the primary or most significant beaches associated with a particular area, region, or body of water.
-
D.
isMajorMarinePassage
Indicates that a waterway serves as a primary route for significant marine or ocean-going vessel traffic.
-
E.
isMajorDeepWaterAreaOf
Indicates that one area constitutes a primary or significant deep-water region of another area or 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
Created at: May 3, 2026, 4:18 p.m.