Triple
T4746139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broadstairs |
E105362
|
entity |
| Predicate | hasProminentActivity |
P44964
|
FINISHED |
| Object | sea bathing |
—
|
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: sea bathing | Statement: [Broadstairs, hasProminentActivity, sea bathing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProminentActivity Context triple: [Broadstairs, hasProminentActivity, sea bathing]
-
A.
hasSignificantActivity
Indicates that an entity exhibits a notable level or intensity of activity, performance, or operation relative to a defined threshold or context.
-
B.
hasPopularActivity
chosen
Indicates that an entity is associated with an activity that is widely favored, frequently engaged in, or well-liked by many people.
-
C.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
D.
hasOnlineActivity
Indicates that an entity engages in or possesses some form of activity or presence on the internet or digital platforms.
-
E.
hasContemporaryActivity
Indicates that two activities occur during the same time period or overlap in 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64ab946481909eccdb3e8c5d1f6a |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6223defc8190823665a6592c1154 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.