Triple
T5194508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notting Hill |
E117235
|
entity |
| Predicate | carnivalTiming |
P14854
|
FINISHED |
| Object | August Bank Holiday weekend |
—
|
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: August Bank Holiday weekend | Statement: [Notting Hill, carnivalTiming, August Bank Holiday weekend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carnivalTiming Context triple: [Notting Hill, carnivalTiming, August Bank Holiday weekend]
-
A.
carnivalRecognizedAs
Indicates that one carnival is acknowledged, designated, or officially regarded as a particular type, status, or identity.
-
B.
ceremonyTiming
chosen
Indicates the temporal relationship specifying when a ceremony occurs or is scheduled to occur.
-
C.
determinesFestival
Indicates that one entity decides, defines, or selects which festival is applicable or will occur for another entity or context.
-
D.
associatedNightTiming
Indicates a relationship where an event, action, or condition is linked specifically to a time period occurring during the night.
-
E.
mainFestival
Indicates that an event is the primary or central festival associated with a particular context, place, or entity.
- 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_69bd4462ed04819084fcb01eb9d2fa74 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7adb034c819086bf8a85fbf158f4 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77b9a67c8190819612257ea746b4 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:46 p.m.