Triple
T36139401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chanson d’Amour |
E1045250
|
entity |
| Predicate | countryOfPopularSuccess |
P86739
|
FINISHED |
| Object | United Kingdom |
E732
|
NE 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: United Kingdom | Statement: [Chanson d’Amour, countryOfPopularSuccess, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfPopularSuccess Context triple: [Chanson d’Amour, countryOfPopularSuccess, United Kingdom]
-
A.
countryOfNotableSuccess
Indicates the country in which an entity achieved notable success or recognition.
-
B.
countryOfPopularPerformance
chosen
Indicates the country where a performance, work, or activity is especially popular or widely received.
-
C.
achievedPopularityVia
Indicates that an entity gained recognition or widespread acceptance through a particular method, channel, or means.
-
D.
coveredCountry
Indicates that one entity includes or provides coverage for the territory or jurisdiction of a specified country.
-
E.
countryFollowedBy
Indicates that one country comes directly after another in a specified sequence or ordering (such as time, ranking, or listing).
- F. None of above.
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_69f76e36a4508190b5bfc8f594272a4c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a023f290e3081909a465d6cfb79518a |
completed | May 11, 2026, 8:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a397d6846bc8190897dda4d1098f4f6 |
completed | June 22, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_6a0238d1436c8190ab0251030b01902e |
completed | May 11, 2026, 8:15 p.m. |
Created at: May 3, 2026, 4:08 p.m.