Triple
T18356933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drive My Car |
E439819
|
entity |
| Predicate | hasProminent |
P30328
|
FINISHED |
| Object | bassline |
—
|
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: bassline | Statement: [Drive My Car, hasProminent, bassline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProminent Context triple: [Drive My Car, hasProminent, bassline]
-
A.
hasProminentAspect
chosen
Indicates that an entity possesses a particularly notable, dominant, or emphasized aspect or feature.
-
B.
hasProminence
Indicates that one entity stands out in importance, visibility, or influence relative to others within a given context.
-
C.
hasProminentSeries
Indicates that an entity is notably associated with a major or well-known series as a defining feature.
-
D.
hasNotablePromoter
Indicates that an entity is actively supported, publicized, or championed by a notable promoter.
-
E.
hasSignificant
Indicates that one entity possesses or exhibits a level of importance, impact, or relevance that is notably large or meaningful in relation to another entity or context.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e516d776cc8190937d7e1d42a36a3b |
completed | April 19, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:37 a.m.