Triple
T35503492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunder Bay |
E1026077
|
entity |
| Predicate | hasShipwrecksFrom |
P186498
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Thunder Bay, hasShipwrecksFrom, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShipwrecksFrom Context triple: [Thunder Bay, hasShipwrecksFrom, 19th century]
-
A.
hasShipwrecks
Indicates that one entity contains, includes, or is associated with shipwrecks located within it or under its control.
-
B.
shipwrecksDisplayedAt
Indicates that shipwrecks are exhibited or presented at a particular location or venue.
-
C.
numberOfShipwrecks
Indicates the quantity of shipwrecks associated with a given entity or context.
-
D.
shipSankIn
Indicates that a specific ship sank (was lost or submerged) in a particular location or body of water.
-
E.
shipwrecksRecoveredIn
Indicates the location or context in which shipwrecks have been found and recovered.
- 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_69f76dfc9c60819089c4217d93922615 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:04 p.m.