Triple
T33888148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mainstage Theatre |
E868684
|
entity |
| Predicate | roleWithinVenue |
P112840
|
FINISHED |
| Object | primary performance space of Queens Theatre |
—
|
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: primary performance space of Queens Theatre | Statement: [Mainstage Theatre, roleWithinVenue, primary performance space of Queens Theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleWithinVenue Context triple: [Mainstage Theatre, roleWithinVenue, primary performance space of Queens Theatre]
-
A.
roleAtFoursquare
Indicates the specific role or position an entity holds at Foursquare.
-
B.
locatedInVenueType
chosen
Indicates that an entity is situated within or associated with a venue of a specific type (e.g., stadium, theater, restaurant).
-
C.
bookingRole
Indicates the role or capacity an entity has in relation to a booking (e.g., who made, manages, or is responsible for the booking).
-
D.
roleAtStadium
Indicates that an entity holds a specific role, function, or position associated with a particular stadium.
-
E.
locatedInOperatedVenue
Indicates that an entity is situated within a venue that is managed or operated by a specified agent or organization.
- 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:48 a.m.