Triple
T33577949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Miller |
E860077
|
entity |
| Predicate | livePerformanceMedium |
P31571
|
FINISHED |
| Object | concerts |
—
|
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: concerts | Statement: [David Miller, livePerformanceMedium, concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livePerformanceMedium Context triple: [David Miller, livePerformanceMedium, concerts]
-
A.
livePerformanceFeature
Indicates that one entity is included or highlighted as a component of another entity’s live performance.
-
B.
livePerformanceStapleFor
Indicates that something (such as a song or piece) is regularly and prominently featured in another entity’s live performances.
-
C.
livePerformer
Indicates that an entity performs an artistic or entertainment act live, typically in front of an audience.
-
D.
livePerformanceContext
Indicates that an action or event occurs within the setting of a live performance, such as a concert, play, or other real-time staged presentation.
-
E.
performsMusicIn
chosen
Indicates that an entity presents or plays music within a particular venue, event, or context.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f74d7f80819084e105cd1e36dabe |
completed | May 3, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:40 a.m.