Triple
T5628091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buddy Guy’s Legends |
E147768
|
entity |
| Predicate | bookingFocus |
P31
|
FINISHED |
| Object | national blues acts |
—
|
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: national blues acts | Statement: [Buddy Guy’s Legends, bookingFocus, national blues acts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bookingFocus Context triple: [Buddy Guy’s Legends, bookingFocus, national blues acts]
-
A.
bookingOption
Indicates a selectable arrangement or choice available for making a booking, such as a specific time, package, or set of conditions under which a reservation can be made.
-
B.
bookingRequirement
Indicates that a particular condition, rule, or prerequisite must be satisfied in order to make or confirm a booking.
-
C.
mainReservation
Indicates that one reservation is designated as the primary or central booking associated with a person, account, or set of related reservations.
-
D.
appointmentBy
Indicates that one entity is appointed or designated to a role, position, or task by another entity.
-
E.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
- 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02239500c8190ad3035e44c3b0670 |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.