Triple
T35541406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexandra Dock, Belfast |
E1027070
|
entity |
| Predicate | hasNotableBerth |
P207042
|
FINISHED |
| Object | HMS Caroline |
E1009447
|
NE 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: HMS Caroline | Statement: [Alexandra Dock, Belfast, hasNotableBerth, HMS Caroline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableBerth Context triple: [Alexandra Dock, Belfast, hasNotableBerth, HMS Caroline]
-
A.
hasBerths
Indicates that one entity provides or contains sleeping or docking berths for another entity.
-
B.
earnedBerthIn
Indicates that one entity has qualified for or secured a place in a particular event, competition, or stage as a result of its performance or achievement.
-
C.
canBerthWith
Indicates that one entity is compatible to dock or berth alongside another entity under specified conditions.
-
D.
hasBerthLength
Indicates the length of a berth allocated to or associated with an entity.
-
E.
hasNotableBay
Indicates that a place possesses a bay that is recognized for its significance, prominence, or special interest.
- F. None of above. chosen
Provenance (5 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3852eb5ee881909aecfe7cb3add09a |
completed | June 21, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:04 p.m.