Triple
T14523380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Good Time |
E340707
|
entity |
| Predicate | hasNotableChartPerformance |
P106518
|
FINISHED |
| Object | international charts |
—
|
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: international charts | Statement: [Good Time, hasNotableChartPerformance, international charts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableChartPerformance Context triple: [Good Time, hasNotableChartPerformance, international charts]
-
A.
hasNotableChartingStatus
chosen
Indicates that an entity has achieved a specific, noteworthy position or performance on an official chart or ranking.
-
B.
notableSingleChartPerformance
Indicates that an entity achieved a particularly significant or distinguished performance on a music singles chart.
-
C.
hasNotablePerformance
Indicates that an entity has delivered a performance that is distinguished, remarkable, or otherwise noteworthy in a particular context.
-
D.
hasNotableChartingVersionBy
Indicates that an entity has a notable charting version created or performed by the specified agent.
-
E.
hasNotablePerformanceIn
Indicates that an entity delivered a significant or distinguished performance within a specified work, event, or context.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea04f16f88190ba357b0f8021b46b |
completed | April 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.