Triple
T24623958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Day Out |
E609485
|
entity |
| Predicate | firstEventHeadliner |
P72079
|
FINISHED |
| Object | Violent Femmes |
—
|
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: Violent Femmes | Statement: [Big Day Out, firstEventHeadliner, Violent Femmes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEventHeadliner Context triple: [Big Day Out, firstEventHeadliner, Violent Femmes]
-
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.
headlinerRingName
Indicates the professional or stage name under which a headlining performer is billed or promoted.
-
C.
firstEditionEvent
Indicates the event at which the first edition or initial release of a work was formally issued or made available.
-
D.
firstPopularPerformer
Indicates that the subject is the earliest performer to achieve notable popularity in a given context or domain.
-
E.
openingMatchCeremonyPerformer
Indicates that an entity performs or participates as an act in the opening ceremony of a match or game event.
- 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_69e2c4d1d3708190a0f2dc6a3a8523bb |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:32 a.m.