Triple
T1823431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morecambe |
E40592
|
entity |
| Predicate | bayNameEtymology |
P19060
|
FINISHED |
| Object | named after Morecambe Bay |
—
|
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: named after Morecambe Bay | Statement: [Morecambe, bayNameEtymology, named after Morecambe Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bayNameEtymology Context triple: [Morecambe, bayNameEtymology, named after Morecambe Bay]
-
A.
seaNameEtymology
chosen
Indicates the origin or derivation of the name given to a particular sea.
-
B.
cityNamedAfter
Indicates that one city derives its name from or was named in honor of another entity, such as a person, place, or concept.
-
C.
districtNameOrigin
Indicates that the relationship specifies the origin or source from which a district’s name is derived.
-
D.
eraName
Indicates the named historical or chronological era associated with an entity or time period.
-
E.
meaningOfNativeName
Indicates that one entity specifies the semantic meaning or translation of another entity’s native-language name.
- 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_69a8864526c081908a3a4d74f689e2c5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab21ab83a48190a33afe5db19a21f8 |
completed | March 6, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69aa61d97d008190b6642aef32eb7e36 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.