Triple
T24879794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No More Doggin' |
E622668
|
entity |
| Predicate | isInfluentialExampleOf |
P69465
|
FINISHED |
| Object | shuffle style |
—
|
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: shuffle style | Statement: [No More Doggin', isInfluentialExampleOf, shuffle style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInfluentialExampleOf Context triple: [No More Doggin', isInfluentialExampleOf, shuffle style]
-
A.
isCanonicalExampleOf
Indicates that something serves as a standard or typical instance that exemplifies a concept, category, or pattern.
-
B.
usedAsExampleIn
Indicates that one entity is cited or presented as an illustrative example within another entity, such as a text, discussion, or explanation.
-
C.
notableExampleAt
Indicates that something serves as a prominent or illustrative example of something else in a particular context or location.
-
D.
notableExampleBy
Indicates that something serves as a prominent or illustrative example provided or created by a particular entity.
-
E.
influentialFrom
chosen
Indicates that one entity has exerted influence on another, contributing to or shaping the latter’s ideas, behavior, or development.
- 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:24 a.m.