Triple
T16374520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Circle |
E397646
|
entity |
| Predicate | primaryPerformanceVenues |
P5078
|
FINISHED |
| Object | European jazz festivals |
—
|
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: European jazz festivals | Statement: [Circle, primaryPerformanceVenues, European jazz festivals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPerformanceVenues Context triple: [Circle, primaryPerformanceVenues, European jazz festivals]
-
A.
primaryVenues
chosen
Indicates the main or most important venues associated with or used by a given entity.
-
B.
primaryVenueFor
Indicates that one entity serves as the main or principal venue or location for events, activities, or operations associated with another entity.
-
C.
intendedPerformanceVenue
Indicates the venue or location where a performance is planned or intended to take place.
-
D.
originalPerformanceVenue
Indicates the venue where a performance was first originally presented or premiered.
-
E.
typicalVenues
Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319d6942081909616a2c6efee9967 |
completed | April 18, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.