Triple
T20311722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Just Lookin’ for a Hit |
E510265
|
entity |
| Predicate | hasCompilationOf |
P8854
|
FINISHED |
| Object | Dwight Yoakam singles |
—
|
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: Dwight Yoakam singles | Statement: [Just Lookin’ for a Hit, hasCompilationOf, Dwight Yoakam singles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompilationOf Context triple: [Just Lookin’ for a Hit, hasCompilationOf, Dwight Yoakam singles]
-
A.
isCompilationOf
chosen
Indicates that one entity is a collected or assembled version made up of multiple other entities.
-
B.
compiledIn
Indicates that a piece of code, program, or module was compiled within or for a specific environment, system, or context.
-
C.
compliedWith
Indicates that one entity has acted in accordance with, or fulfilled the requirements of, another entity’s rules, requests, or standards.
-
D.
workCompiledIn
Indicates that a work has been gathered, edited, or assembled into a larger collection, volume, or compilation.
-
E.
compilesWorkOf
Indicates that one entity gathers, edits, or assembles the works created by another entity into a collection or compilation.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e677441f9c8190acf98dc92c77732b |
completed | April 20, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:19 a.m.