Triple
T34974366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prelude to Joanie |
E1008630
|
entity |
| Predicate | isIntroFor |
P117488
|
FINISHED |
| Object | Joanie's Butterfly |
—
|
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: Joanie's Butterfly | Statement: [Prelude to Joanie, isIntroFor, Joanie's Butterfly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIntroFor Context triple: [Prelude to Joanie, isIntroFor, Joanie's Butterfly]
-
A.
hasIntro
Indicates that an entity includes or is associated with an introductory section or opening part.
-
B.
hasIntroduction
Indicates that one entity includes or provides an introductory section, part, or presentation for another entity.
-
C.
isIntroTrack
chosen
Indicates that a track serves as the introductory piece, typically opening or setting the stage for the rest of a collection (such as an album, playlist, or set).
-
D.
canIntroduce
Indicates that one entity has the ability or permission to introduce another entity to a third party or context.
-
E.
isAbout
Indicates that one entity has as its subject, focus, or primary concern the content, topic, or theme represented by another entity.
- 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.