Triple
T1110336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tunbridge Wells Fringe Festival |
E25580
|
entity |
| Predicate | usesVenueType |
P10640
|
FINISHED |
| Object | theatres |
—
|
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: theatres | Statement: [Tunbridge Wells Fringe Festival, usesVenueType, theatres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesVenueType Context triple: [Tunbridge Wells Fringe Festival, usesVenueType, theatres]
-
A.
refersToVenueType
chosen
Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
-
B.
usualVenueSince
Indicates that a particular venue has been the regular or customary location for something (e.g., an event or activity) starting from a specified point in time.
-
C.
servesVenue
Indicates that an entity provides services or functions in support of a particular venue.
-
D.
homeVenueOwned
Indicates that the specified home venue is legally owned or possessed by the associated entity.
-
E.
venueSelection
Indicates the relationship in which a specific venue is chosen or designated for an event, activity, or purpose among available options.
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bbd92a8c8190a16e55f3f739010f |
completed | March 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69a4bb42990c819080db96478fd4977e |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.