Triple
T20013902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Non, je ne regrette rien |
E494659
|
entity |
| Predicate | isIconicWorkFor |
P43625
|
FINISHED |
| Object | French chanson genre |
—
|
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: French chanson genre | Statement: [Non, je ne regrette rien, isIconicWorkFor, French chanson genre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIconicWorkFor Context triple: [Non, je ne regrette rien, isIconicWorkFor, French chanson genre]
-
A.
isIconicIn
chosen
Indicates that something is widely recognized as a defining or emblematic example within a particular context, domain, or location.
-
B.
movementRepresentativeWorkOf
Indicates that a work is considered a key or emblematic example representing a particular movement.
-
C.
isLesserKnownWorkOf
Indicates that one work is a less famous or less widely recognized creation of a particular creator or artist.
-
D.
namedForNotableWork
Indicates that one entity is named in honor of another entity’s notable work or achievement.
-
E.
isSeminalWorkOf
Indicates that a work is a foundational or highly influential creation associated with a particular person, field, or body of work.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623a9bd48190a3344a07540170c7 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:34 p.m.