Triple
T29676617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Now & Then |
E750834
|
entity |
| Predicate | sideTwoConcept |
P5443
|
FINISHED |
| Object | oldies radio show format |
—
|
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: oldies radio show format | Statement: [Now & Then, sideTwoConcept, oldies radio show format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideTwoConcept Context triple: [Now & Then, sideTwoConcept, oldies radio show format]
-
A.
side2
chosen
Indicates that an entity is positioned on, associated with, or corresponds to the second side of another entity or structure.
-
B.
side2Strength
Indicates the magnitude or level of strength associated with the second side in a relationship, comparison, or interaction.
-
C.
side2Leader
Indicates that the referenced entity serves as the leader or primary representative of the second side in a two-sided relationship, interaction, or conflict.
-
D.
controlledBySide2
Indicates that the object or resource is under the control, authority, or influence of the second party or side in a relationship or interaction.
-
E.
side
Indicates that one entity is located at, aligned with, or associated with the lateral part or edge of another entity.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6725dadb081909ef2fbba8d3fd935 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:07 p.m.