Triple
T7336410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grant Park victory speech 2008-11-04 |
E169137
|
entity |
| Predicate | transcriptAvailable |
P77108
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Grant Park victory speech 2008-11-04, transcriptAvailable, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transcriptAvailable Context triple: [Grant Park victory speech 2008-11-04, transcriptAvailable, yes]
-
A.
hasSpeech
Indicates that an entity produces, delivers, or is associated with a spoken utterance or verbal expression.
-
B.
recordingOf
Indicates that one entity is an audio or video capture or performance that documents, represents, or preserves another entity (such as a work, event, or expression).
-
C.
hasVoiceIn
Indicates that an entity participates by providing a voice role or vocal performance in another entity, such as a work, production, or recording.
-
D.
transcription
Indicates the process by which genetic information in DNA is copied into RNA by RNA polymerase.
-
E.
voiceWork
Indicates that one entity performs or contributes voice acting or vocal performance work for another entity or creative production.
- 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_69c68a568a6481908f11e20db7bc8446 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f347f25081908e6086d4073295f5 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f028fd748190b2ea5c3081958a42 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f3463d0481908aed9ed43a8ac6a8 |
completed | March 27, 2026, 9:14 p.m. |
Created at: March 27, 2026, 3:04 p.m.