Triple
T34993141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Caroline |
E1009447
|
entity |
| Predicate | mooredIn |
P8968
|
FINISHED |
| Object | Alexandra Dock, Belfast |
—
|
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: Alexandra Dock, Belfast | Statement: [HMS Caroline, mooredIn, Alexandra Dock, Belfast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mooredIn Context triple: [HMS Caroline, mooredIn, Alexandra Dock, Belfast]
-
A.
mooredAt
chosen
Indicates that one object, typically a vessel or floating structure, is secured or anchored at a specific location or facility.
-
B.
mooredInState
Indicates that an object such as a vessel or structure is secured or anchored within the territorial waters or jurisdiction of a specific state.
-
C.
mooredInCountry
Indicates that a vessel or floating structure is secured or docked within the territorial waters or ports of a specified country.
-
D.
mooringType
Indicates the specific method or system by which a vessel or floating structure is secured in place.
-
E.
berthingOrDockingTarget
Indicates that an entity serves as the location or structure where a vessel or vehicle is intended to berth or dock.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.