Triple
T15971304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Pablo Tour |
E387328
|
entity |
| Predicate | closingShowNote |
P120668
|
FINISHED |
| Object | final show ended early |
—
|
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: final show ended early | Statement: [Saint Pablo Tour, closingShowNote, final show ended early]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closingShowNote Context triple: [Saint Pablo Tour, closingShowNote, final show ended early]
-
A.
closingNarrationBy
Indicates that a particular entity serves as the narrator delivering the closing or final narration of a work or segment.
-
B.
closingSection
Indicates that one entity serves as the concluding or final section of another entity (such as a document, event, or structured sequence).
-
C.
closingTopic
Indicates that one entity brings a discussion, issue, or conversational thread to an end or final resolution.
-
D.
closingTheme
Indicates that one entity serves as the ending or closing theme (such as a song or musical piece) associated with another entity, typically a media work or episode.
-
E.
closingStimulus
Indicates that one entity serves as the stimulus or trigger that causes another entity to close or become closed.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e173af801c8190bfc0f602831bb594 |
completed | April 16, 2026, 11:41 p.m. |
Created at: April 10, 2026, 4:54 a.m.