Triple
T4650043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Last Waltz (concert) |
E102269
|
entity |
| Predicate | billedAs |
P8467
|
FINISHED |
| Object | farewell concert of The Band |
—
|
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: farewell concert of The Band | Statement: [The Last Waltz (concert), billedAs, farewell concert of The Band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: billedAs Context triple: [The Last Waltz (concert), billedAs, farewell concert of The Band]
-
A.
billedFrom
Indicates that a bill, invoice, or charge originates from or is issued by a particular source or entity.
-
B.
isTypicallySoldAs
Indicates that one entity is commonly offered for sale in the form, packaging, or configuration represented by another entity.
-
C.
builtOnBehalfOf
Indicates that something was constructed or created by one party acting as a representative or agent for another party.
-
D.
billedWeight
Indicates the weight value used for billing or charging purposes in a transaction or shipment.
-
E.
announcedAs
chosen
Indicates that one entity is publicly presented, declared, or introduced in a specified role, name, or capacity by 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_69bd43d71a308190afea7280841b0de8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6632708c8190b627d99363ab062c |
completed | March 20, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69bd620fc5e081908325ac8e6a6384ab |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:14 p.m.