Triple
T533849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morecambe Bay |
E12282
|
entity |
| Predicate | hasTraditionalActivity |
P971
|
FINISHED |
| Object | guided cross-bay walks |
—
|
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: guided cross-bay walks | Statement: [Morecambe Bay, hasTraditionalActivity, guided cross-bay walks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalActivity Context triple: [Morecambe Bay, hasTraditionalActivity, guided cross-bay walks]
-
A.
hasTraditionalSymbol
Indicates that something is associated with or represented by a conventional or culturally established symbol.
-
B.
hasRecreationActivity
chosen
Indicates that an entity provides, includes, or is associated with a particular recreational activity.
-
C.
hasActivityStatus
Indicates the current state or condition of an activity, such as whether it is planned, ongoing, completed, or cancelled.
-
D.
traditionallyOneOf
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
-
E.
hasLegacy
Indicates that an entity leaves behind a lasting impact, influence, or inheritance that continues to exist or be recognized over time.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b3e49081909810fa417b31306f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.