Triple
T35958823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edmund Fitzgerald shipwreck |
E1039940
|
entity |
| Predicate | bellDisplayedAt |
P3021
|
FINISHED |
| Object | Great Lakes Shipwreck Museum, Whitefish Point |
—
|
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: Great Lakes Shipwreck Museum, Whitefish Point | Statement: [Edmund Fitzgerald shipwreck, bellDisplayedAt, Great Lakes Shipwreck Museum, Whitefish Point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bellDisplayedAt Context triple: [Edmund Fitzgerald shipwreck, bellDisplayedAt, Great Lakes Shipwreck Museum, Whitefish Point]
-
A.
displayedAt
chosen
Indicates that one entity is presented or exhibited at a particular location, venue, or event.
-
B.
bellOrientation
Indicates the spatial direction or alignment in which a bell is positioned or facing.
-
C.
bellPattern
Indicates that one entity exhibits or follows a bell-shaped or bell-like pattern in relation to another entity or variable.
-
D.
bellPeriod
Indicates the specific time interval or class period during which a bell rings or is scheduled to ring.
-
E.
bellSize
Indicates a relationship where an entity is characterized or classified by the size of a bell associated with it.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.