Triple
T13747504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US Hot Gospel Songs |
E330253
|
entity |
| Predicate | hasUnitOfAnalysis |
P33307
|
FINISHED |
| Object | individual songs |
—
|
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: individual songs | Statement: [US Hot Gospel Songs, hasUnitOfAnalysis, individual songs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnitOfAnalysis Context triple: [US Hot Gospel Songs, hasUnitOfAnalysis, individual songs]
-
A.
unitOfAnalysis
chosen
Indicates the primary entity, level, or component that is being examined or measured in a given analysis or study.
-
B.
statisticalUnitOf
Indicates that one entity serves as the statistical unit (the basic unit of observation or analysis) for which data or statistics are collected or reported about another entity.
-
C.
samplingUnit
Indicates that one entity serves as the basic unit or element from which samples are drawn or measured in a sampling process.
-
D.
hasUnitOf
Indicates that a quantity, measurement, or value is expressed in terms of a specific unit.
-
E.
hasUnitStructure
Indicates that an entity possesses a specific internal organization or arrangement that defines its structural composition.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02132a108190aca728b95e83af01 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:08 p.m.