Triple
T5489462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanyadaan |
E123663
|
entity |
| Predicate | performanceVenueType |
P10640
|
FINISHED |
| Object | proscenium 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: proscenium theatre | Statement: [Kanyadaan, performanceVenueType, proscenium theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceVenueType Context triple: [Kanyadaan, performanceVenueType, proscenium theatre]
-
A.
typicalVenues
Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
-
B.
refersToVenueType
chosen
Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
-
C.
typeOfPerformances
Indicates the kinds or categories of performances associated with or offered by an entity.
-
D.
legacyVenue
Indicates that a venue has historical or long-standing significance, often preserved or recognized due to its past importance or enduring role.
-
E.
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.
- 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd93e5d0f08190a6cc9fc408b7c5bb |
completed | March 20, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69bd91a73b148190a865243536a4fe76 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:10 p.m.