Triple
T5675201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Ribfest |
E125068
|
entity |
| Predicate | heldDuringSeason |
P45371
|
FINISHED |
| Object | summer |
—
|
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: summer | Statement: [London Ribfest, heldDuringSeason, summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldDuringSeason Context triple: [London Ribfest, heldDuringSeason, summer]
-
A.
occurredInSeason
chosen
Indicates that an event or occurrence took place during a specific season within a temporal sequence (such as a TV show season or sports season).
-
B.
playsInSeason
Indicates that an entity participates or performs in a specific season of an ongoing series, competition, or event.
-
C.
playedInSeason
Indicates that an entity (such as a player or participant) took part in or was active during a specific season.
-
D.
usedInSeason
Indicates that something (such as an item, strategy, or element) is utilized or appears within a particular season.
-
E.
positionInSeason
Indicates the specific ordinal placement or ranking of something within the sequence of items in a season.
- 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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025303860819093e51f176babed71 |
completed | March 22, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69c021bc3894819084f37d14ba4b2644 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:43 p.m.