Triple
T15584652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live at the Beacon Theater |
E374585
|
entity |
| Predicate | priceAtInitialRelease |
P4148
|
FINISHED |
| Object | 5 USD |
—
|
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: 5 USD | Statement: [Live at the Beacon Theater, priceAtInitialRelease, 5 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: priceAtInitialRelease Context triple: [Live at the Beacon Theater, priceAtInitialRelease, 5 USD]
-
A.
actualLaunchPrice
chosen
Indicates the price at which something was actually launched or first offered, as opposed to its planned or advertised launch price.
-
B.
kitPriceAtIntroduction
Indicates the price assigned to a kit at the time it was first introduced or made available.
-
C.
assembledPriceAtIntroduction
Indicates the price assigned to an assembled product at the time it is first introduced or launched.
-
D.
launchPriceDescription
Indicates the descriptive text explaining the initial price at which a product or service is first launched or offered.
-
E.
acquisitionCost
Indicates the monetary amount or value required to obtain or purchase an 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e47971481909e986dd999354628 |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:11 a.m.