Triple
T20386694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brockworth, Gloucestershire, England |
E497975
|
entity |
| Predicate | cheeseRollingAttracts |
P139928
|
FINISHED |
| Object | international competitors |
—
|
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: international competitors | Statement: [Brockworth, Gloucestershire, England, cheeseRollingAttracts, international competitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cheeseRollingAttracts Context triple: [Brockworth, Gloucestershire, England, cheeseRollingAttracts, international competitors]
-
A.
hasCheeseVarietyNamedAfterIt
Indicates that something has a type or variety of cheese that is named after it.
-
B.
cheeseMarketDay
Indicates a specific day designated for buying, selling, or trading cheese in a market setting.
-
C.
cheeseSpeciality
Indicates that one entity is known for or specializes in producing or offering a particular type of cheese.
-
D.
Sneekweek
Indicates participation in or association with the Dutch student sailing and water sports event known as Sneekweek.
-
E.
cheeseType
Indicates that one entity is a specific type or variety of cheese in relation to another entity.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6790bcef481909453d19c846ab420 |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:28 a.m.