Triple
T34846582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Box (Freespace black box theatre) |
E1004485
|
entity |
| Predicate | hasParentVenue |
P65326
|
FINISHED |
| Object | Freespace |
—
|
NE NERFINISHED |
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: Freespace | Statement: [The Box (Freespace black box theatre), hasParentVenue, Freespace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentVenue Context triple: [The Box (Freespace black box theatre), hasParentVenue, Freespace]
-
A.
hasAttachedVenue
Indicates that one entity has another entity linked or associated with it as a venue.
-
B.
hasPrincipalVenue
chosen
Indicates that an entity has a primary or main venue where its activities, events, or operations predominantly take place.
-
C.
hasVenueIn
Indicates that an event, activity, or occurrence takes place at a specific venue located within a particular geographic area or location.
-
D.
hasVenueOwner
Indicates that a particular venue is owned or controlled by a specific owner.
-
E.
hasVenueFor
Indicates that one entity provides or serves as the location or setting where an event, activity, or function takes place for another entity.
- 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffab5adf2c819084700c5ea34615bf |
completed | May 9, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69ffaabffa208190b5214ca17cc8a5ea |
completed | May 9, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4 p.m.