Triple
T35666326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western World |
E1030571
|
entity |
| Predicate | ticketPriceInUniverse |
P184068
|
FINISHED |
| Object | $1,000 per day (in-film dialogue) |
—
|
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: $1,000 per day (in-film dialogue) | Statement: [Western World, ticketPriceInUniverse, $1,000 per day (in-film dialogue)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketPriceInUniverse Context triple: [Western World, ticketPriceInUniverse, $1,000 per day (in-film dialogue)]
-
A.
ticketPricePlanned
Indicates that a ticket has an intended or scheduled price set in advance, as opposed to its actual or current selling price.
-
B.
averageTicketPrice
Indicates the typical or mean price paid per ticket in a given context or transaction set.
-
C.
ticketPricingLevel
Indicates the pricing tier or category assigned to a ticket within a defined pricing structure.
-
D.
ticketPricePolicy
Indicates the pricing rules or conditions that determine how much a ticket costs in a given context.
-
E.
ticketPriceMaximum
Indicates the highest allowable or recorded price for a ticket within a given context or transaction.
- F. None of above. chosen
Provenance (4 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:05 p.m.