Triple
T10750102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upside Down |
E253549
|
entity |
| Predicate | chartPositionSouthAfricaSpringbokRadio |
P36876
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Upside Down, chartPositionSouthAfricaSpringbokRadio, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chartPositionSouthAfricaSpringbokRadio Context triple: [Upside Down, chartPositionSouthAfricaSpringbokRadio, 1]
-
A.
chartPositionSouthAfrica
chosen
Indicates the position or ranking something holds on a chart or listing specifically within South Africa.
-
B.
chartPositionRhodesia
Indicates the chart ranking or position achieved in Rhodesia for the item in question.
-
C.
chartPositionZimbabwe
Indicates the position or ranking of something on a music or performance chart specifically within Zimbabwe.
-
D.
chartPositionAustralia
Indicates the position or ranking of something on a music or sales chart specifically within Australia.
-
E.
chartPositionUnitedKingdom
Indicates the position or rank something holds on a music or sales chart specifically within the United Kingdom.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d71dbfe5f481908eed42328447b158 |
completed | April 9, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:15 p.m.