Triple
T23562255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Father and Son |
E579272
|
entity |
| Predicate | chartingSingleVersionBy |
P60345
|
FINISHED |
| Object | Boyzone |
—
|
NE NERFINISHED |
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: Boyzone | Statement: [Father and Son, chartingSingleVersionBy, Boyzone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chartingSingleVersionBy Context triple: [Father and Son, chartingSingleVersionBy, Boyzone]
-
A.
chartingVersionBy
Indicates that one entity serves as the versioning or revision source by which another entity’s chart or graphical representation is defined or organized.
-
B.
chartingSingle
chosen
Indicates that an entity appears on a music chart as a single track release.
-
C.
hasChartingVersion
Indicates that one entity is associated with a specific version of charting or visualization used to represent its data or configuration.
-
D.
chartStatus
Indicates the current state or condition of a chart, such as whether it is active, updated, or in a particular workflow stage.
-
E.
historicalVersion
Indicates that one entity represents an earlier or past version in the history or evolution 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_69e245fe24588190888f3aec8407d8e3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af68cddc8190ab9d0b7ee1f157ed |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:23 p.m.