Triple
T35966489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Daniel J. Morrell shipwreck |
E1040155
|
entity |
| Predicate | brokeInTwo |
P184292
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [SS Daniel J. Morrell shipwreck, brokeInTwo, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brokeInTwo Context triple: [SS Daniel J. Morrell shipwreck, brokeInTwo, yes]
-
A.
brokenIn
Indicates that an object or system has become nonfunctional or damaged while located within or inside a particular place, context, or container.
-
B.
broke
Indicates that one entity caused another entity to separate into pieces or cease functioning, typically through force or damage.
-
C.
brokeUpIn
Indicates that a romantic or close relationship between entities ended in a specified location or context.
-
D.
brokenOn
Indicates that an object or system ceased functioning or became damaged at a specific time or on a specific date.
-
E.
broken
Indicates that an entity is damaged or no longer functioning as intended, often as the result of some prior action or event.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ad15f3b88190b7c9742a734fec5f |
completed | May 3, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7acad20388190b9b10270ca9bdfbc |
completed | May 3, 2026, 8:14 p.m. |
Created at: May 3, 2026, 4:07 p.m.