Triple
T25145171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sur le pont d’Avignon |
E629912
|
entity |
| Predicate | performanceLocationInLyrics |
P67218
|
FINISHED |
| Object | on the bridge of Avignon |
—
|
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: on the bridge of Avignon | Statement: [Sur le pont d’Avignon, performanceLocationInLyrics, on the bridge of Avignon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceLocationInLyrics Context triple: [Sur le pont d’Avignon, performanceLocationInLyrics, on the bridge of Avignon]
-
A.
hasKeyLocationInLyrics
chosen
Indicates that a key or central location is mentioned or referenced within the lyrics.
-
B.
lyricReference
Indicates that one entity (typically a work or text) contains or makes a reference to the lyrics of another entity.
-
C.
performerLocation
Indicates that an entity is located at, performing at, or associated with a specific place or venue.
-
D.
lyricFocus
Indicates that the primary emphasis or subject of the lyrics is centered on a particular entity or theme.
-
E.
scriptUsedInLyrics
Indicates that a particular writing system or script is used to write or represent the lyrics of a song or musical 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 6:29 a.m.