Triple
T24701852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hebridean Celtic Festival |
E611767
|
entity |
| Predicate | hasHeadliner |
P72079
|
FINISHED |
| Object | Capercaillie |
—
|
NE NERFINISHED |
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: Capercaillie | Statement: [Hebridean Celtic Festival, hasHeadliner, Capercaillie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeadliner Context triple: [Hebridean Celtic Festival, hasHeadliner, Capercaillie]
-
A.
headlinedBy
chosen
Indicates that something (such as an event, show, or publication) is led, featured, or given top billing by a particular main performer, act, or entity.
-
B.
hasHeadOf
Indicates that one entity serves as the leader, chief, or person in charge of another entity (such as an organization, group, or department).
-
C.
headlinerRingName
Indicates the professional or stage name under which a headlining performer is billed or promoted.
-
D.
hasNotablePerformer
Indicates that an entity features or is associated with a performer who is particularly prominent, famous, or otherwise noteworthy.
-
E.
hasFeaturedArtist
Indicates that an entity (such as a song or track) includes another artist who appears as a featured performer.
- 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_69e2c4d76d148190b58ad612467149a5 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 3:23 a.m.