Triple
T24398596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Darlin' |
E615101
|
entity |
| Predicate | isPopularStandardIn |
P156051
|
FINISHED |
| Object | oldies radio |
—
|
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 | Statement: [Little Darlin', isPopularStandardIn, oldies radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPopularStandardIn Context triple: [Little Darlin', isPopularStandardIn, oldies radio]
-
A.
isPopularStandard
Indicates that something is widely accepted, commonly used, and recognized as a prevailing or de facto standard.
-
B.
isPopularStandardFor
Indicates that something is widely accepted and commonly used as the standard choice for a particular purpose or context.
-
C.
isPopularStandardFrom
Indicates that something is widely recognized and commonly adopted as a standard originating from a particular source or provider.
-
D.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
E.
isStandardOn
Indicates that a particular feature, option, or component is included by default as part of another item, rather than being optional or extra.
- F. None of above. chosen
Provenance (4 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_69e2d7e509b88190a53155d4f3de45ce |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294d85db08190b4c63ea6b7b74438 |
completed | April 29, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:05 a.m.