Triple
T10904535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Great Escape (music festival) |
E257531
|
entity |
| Predicate | hasApproximateNumberOfVenuesPerEdition |
P14673
|
FINISHED |
| Object | 30+ |
—
|
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: 30+ | Statement: [The Great Escape (music festival), hasApproximateNumberOfVenuesPerEdition, 30+]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateNumberOfVenuesPerEdition Context triple: [The Great Escape (music festival), hasApproximateNumberOfVenuesPerEdition, 30+]
-
A.
numberOfVenues
chosen
Indicates the total count of venues associated with a given entity or context.
-
B.
hasFestivalFrequency
Indicates how often a festival or recurring celebratory event takes place within a given time period.
-
C.
screeningsPerEdition
Indicates the number of screenings associated with each edition of an event or series.
-
D.
exhibitionFrequency
Indicates how often an entity is displayed, presented, or exhibited within a given context or time period.
-
E.
eventEdition
Indicates a specific version or iteration of an event within a recurring or multi-edition series.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d761a5dffc8190927b0928978646a4 |
completed | April 9, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69d70d3d69e08190bb369e9a7927142c |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:22 p.m.