Triple
T2908999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Goliath |
E63635
|
entity |
| Predicate | brokenUp |
P42685
|
FINISHED |
| Object | 1815 |
—
|
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: 1815 | Statement: [HMS Goliath, brokenUp, 1815]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brokenUp Context triple: [HMS Goliath, brokenUp, 1815]
-
A.
broken
Indicates that an entity is damaged or no longer functioning as intended, often as the result of some prior action or event.
-
B.
breaksUpWith
Indicates that one entity ends a romantic or intimate relationship with another entity.
-
C.
breaksWith
Indicates that one entity ends or disrupts an existing association, agreement, or alignment with another entity.
-
D.
breakUpSeason
Indicates the time of year or season during which a romantic relationship ends or a breakup occurs.
-
E.
breakupLinkedTo
Indicates a causal or associative relationship where a breakup is connected to, influenced by, or results from another event, factor, or entity.
- F. None of above. chosen
Provenance (4 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0d329c88190b6fcaef0be1799eb |
completed | March 7, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69abdd19bac881908f047d616aca8438 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abdd96670c8190b727f9ac27dadf67 |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 10:11 p.m.