Triple
T18148822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robbie Williams: Live at Knebworth |
E434453
|
entity |
| Predicate | eventTypeCaptured |
P130637
|
FINISHED |
| Object | live concert |
—
|
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: live concert | Statement: [Robbie Williams: Live at Knebworth, eventTypeCaptured, live concert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventTypeCaptured Context triple: [Robbie Williams: Live at Knebworth, eventTypeCaptured, live concert]
-
A.
captureEvent
Indicates an event in which one entity successfully takes control, possession, or custody of another entity.
-
B.
eventContext
Indicates the situational or background circumstances (such as time, place, conditions, or surrounding events) within which a particular event occurs or is interpreted.
-
C.
eventCommanded
Indicates that one entity issued an order or directive for another entity to carry out a specific event or action.
-
D.
eventLevel
Indicates the intensity, magnitude, or severity associated with an event within a defined scale or hierarchy.
-
E.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
- F. None of above. chosen
Provenance (4 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de372e8081908b52fe33c870716e |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:29 a.m.