Triple
T1672736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prom at the Palace |
E36160
|
entity |
| Predicate | ticketAllocationMethod |
P9552
|
FINISHED |
| Object | public ballot |
—
|
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: public ballot | Statement: [Prom at the Palace, ticketAllocationMethod, public ballot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketAllocationMethod Context triple: [Prom at the Palace, ticketAllocationMethod, public ballot]
-
A.
seatNotationSystem
Indicates the system or convention used to label, number, or otherwise denote seats within a venue or vehicle.
-
B.
seatSelectionPolicy
chosen
Indicates the rules or constraints governing how seats are chosen or assigned in a given context.
-
C.
qualificationSpotAllocation
Indicates the assignment of available qualification spots or slots to entities based on predefined criteria or results.
-
D.
hasTicketing
Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
-
E.
ticketDemand
Indicates that there is a level of desire or need among potential buyers for tickets to an event, service, or offering.
- 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_69a8861286808190939afff3ce8ee31e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab272a653481908f48aa1eed5de8a4 |
completed | March 6, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69aa61b2f6288190b2348ef7d7e4672d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.