Triple
T28550741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sale and Pelletier |
E722878
|
entity |
| Predicate | notableProgramMusic |
P36596
|
FINISHED |
| Object | Love Story by Francis Lai |
—
|
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: Love Story by Francis Lai | Statement: [Sale and Pelletier, notableProgramMusic, Love Story by Francis Lai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableProgramMusic Context triple: [Sale and Pelletier, notableProgramMusic, Love Story by Francis Lai]
-
A.
notableTune
Indicates that a tune is especially significant, well-known, or characteristic in relation to a particular entity.
-
B.
notableComposition
chosen
Indicates that an entity is a significant or well-known work created by another entity, such as a notable musical, literary, or artistic composition.
-
C.
notableRecordingType
Indicates that the subject is notably associated with recordings of a particular type or format.
-
D.
notableProgramType
Indicates that the subject is recognized for or associated with a particular type or category of program.
-
E.
notableConcert
Indicates that a concert event is recognized as particularly significant, memorable, or influential in some notable way.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a013632a3048190b05716d803f34716 |
completed | May 11, 2026, 1:51 a.m. |
| PD | Predicate disambiguation | batch_6a01309582e48190a05d47d96ffb7a46 |
completed | May 11, 2026, 1:27 a.m. |
Created at: April 28, 2026, 3:42 a.m.