Triple
T14183189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theatertreffen |
E351506
|
entity |
| Predicate | typeOfVenueUsed |
P78175
|
FINISHED |
| Object | Berlin 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: Berlin theatres | Statement: [Theatertreffen, typeOfVenueUsed, Berlin theatres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfVenueUsed Context triple: [Theatertreffen, typeOfVenueUsed, Berlin theatres]
-
A.
home venue type
Indicates the kind or category of place that serves as the primary location where an entity regularly hosts its events or activities.
-
B.
homeVenueDuration
Indicates the length of time an entity uses or has used a particular venue as its home location for events or activities.
-
C.
usesVenues
chosen
Indicates that one entity makes use of or operates within specific venues or locations to carry out its activities or services.
-
D.
homeVenueAlsoUsedBy
Indicates that the venue serving as a home location for one entity is also used as a venue by another entity.
-
E.
venue
Indicates the place or location where an event, activity, or interaction takes place.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61cc0a848190b660095972b1223b |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:03 a.m.