Triple
T28980620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Filey Bay |
E734537
|
entity |
| Predicate | hasBeachAwardStatus |
P36406
|
FINISHED |
| Object | popular family beach |
—
|
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: popular family beach | Statement: [Filey Bay, hasBeachAwardStatus, popular family beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeachAwardStatus Context triple: [Filey Bay, hasBeachAwardStatus, popular family beach]
-
A.
awardedStatus
chosen
Indicates that a particular status, honor, or designation has been formally granted to an entity.
-
B.
hasAwardLevel
Indicates that an entity possesses or has been assigned a specific level, tier, or rank within an award or recognition system.
-
C.
hasAwarded
Indicates that one entity has given or conferred an award to another entity.
-
D.
hasAwardConnection
Indicates a relationship where an entity is connected to an award, such as by receiving, being nominated for, or otherwise associated with that award.
-
E.
isAwardedWithin
Indicates that an award or recognition is granted to an entity within a specified context, scope, or time frame.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 28, 2026, 9:11 a.m.